Oracle^® Business Intelligence Applications Installation and Configuration Guide > Integrated Security for Oracle BI Applications >

Types of Security in Oracle BI

Two different levels of security configuration are supported by Oracle Business Intelligence:

• Data-level security
• Object-level security

Oracle Business Intelligence applications security is based on Responsibilities, Positions, and Oracle Business Intelligence repository groups. A Repository group and a Presentation Services group are created for each Oracle Business Intelligence-specific responsibility defined in the Siebel (CRM) or Oracle E-Business Suite operational application. The group names are exactly the same as the responsibility name.

In a Siebel (CRM) or Oracle E-Business Suite operational application, you assign users to the appropriate Analytics responsibilities, and the membership is automatically reflected in the repository as well as the in Presentation Services. The user inherits the appropriate permissions from the responsibilities.

NOTE:  Users should always be created in the operational application databases or directory services such as LDAP, never in the Oracle Business Intelligence repository. For details on integration with Oracle E Business Suite please refer to the section Implementing Security With Oracle EBS.

User Access and User Responsibilities

In previous releases (that is, prior to the 7.9 release), permission and access were determined by user's memberships in various responsibilities.

In this release, new security groups have been introduced in the Analytics repository only, which are based on the position hierarchy level of the user. The administrator can check which group a user belongs to by opening the repository in online mode (while the user is logged in) and checking the value of the HIER_LEVEL variable in Manage\Sessions screen. These groups are called:

• Hierarchy Level (Base), Hierarchy Level 1 to Hierarchy Level 8
• Hierarchy Level (Top)

A user is assigned dynamically to one of these groups at Login time. For more information on these new groups, see Filters for Oracle BI Security Groups.

For all other responsibilities, the term Responsibility is interchangeable with the terms Repository group and Presentation Services group; they have a one-to-one correspondence.

Oracle Business Intelligence come with certain pre-configured responsibilities. Table 103 shows these pre-configured responsibilities.

Checking Analytics Applications User Responsibilities

There are two ways for an Administrator to check a user's responsibility:

• In the Siebel or Oracle E-Business Suite operational application, go to the Responsibilities view.
• Go to the Oracle BI Web and click the My Account link.

  The group membership for the user is shown near the bottom of the Web page.

Registering a New User Responsibility in CRM Analytics Applications

When you add a new responsibility to a user in Oracle BI Web, the change is not immediately reflected in the Oracle BI environment. In order to register the new user responsibility, both the Administrator and the user must perform a task:

• The Oracle BI Administrator must reload the Server metadata through Oracle BI Web.
• After the metadata is reloaded, the user must log out from the Siebel or Oracle E-Business Suite operational application, then log in again.

Default Security Settings in CRM Analytics Applications

The User Administrator and the Group Administrators are a special user and group that do not have any restrictions and do not go through the Siebel or Oracle E-Business Suite database. The User SADMIN (password SADMIN) is also a special user, similar to Administrator.

NOTE:  Be sure to change the default password before migrating to production.

The Administrator group is set up as a member of the supergroup Administrators, so members of this group have no restrictions.