SSE_ROLE & Securities
(Doc ID 497920.1)
Last updated on JULY 12, 2021
Applies to:Siebel System Software - Version 18.104.22.168  and later
Siebel CRM - Version 7.5.3  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (MidMarket)
Version: 22.214.171.124  MME and later including 15,16,17
Database: Oracle 126.96.36.199 and above
*** Checked for relevancy 27-Feb-2013 ***
Application Server OS: Any
Database Server OS: Any
This document was previously published as Siebel SR 38-1166699088.
After the customer's security team had reviewed the Siebel installation environement they came up with many suggestions regarding the security of this installation. Requesting advice on the following:
User authentication in Siebel is performed directly through Oracle Server DB account.
The customer is not using LDAP or any other 3thd party method of authentication.
When installing the system, the SSE_ROLE role is created on the Oracle instance and all objects that are created under the SIEBEL schema are granted to this role. Later the users will be assigned this role.
Can we create a sub-set of this default role on the Oracle instance, and prevent the users from access to a few critical tables?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document