| Oracle® Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) Part Number E10543-04 |
|
|
View PDF |
| Oracle® Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) Part Number E10543-04 |
|
|
View PDF |
This chapter introduces the Oracle Business Intelligence security model, discusses the tools used to configure security, and provides a detailed roadmap for configuring security in Oracle Business Intelligence.
Note:
For a high-level roadmap for setting up security, see Section 1.1, "High-level Roadmap for Setting Up Security In Oracle Business Intelligence".This chapter contains the following sections:
Section 1.1, "High-level Roadmap for Setting Up Security In Oracle Business Intelligence"
Section 1.2, "Overview of Security in Oracle Business Intelligence"
Section 1.5, "About Pre Configured Users, Groups, and Application Roles"
Section 1.6, "What Tools Configure Security in Oracle Business Intelligence?"
Section 1.7, "Example: Looking at the Installed Users, Groups, and Application Roles"
Section 1.8, "Detailed List of Steps for Setting Up Security In Oracle Business Intelligence"
Section 1.9, "Comparing the Oracle Business Intelligence 10g and 11g Security Models"
To set up security in Oracle Business Intelligence, you must do the following:
Read the rest of this chapter 'Introduction to Security in Oracle Business Intelligence' to get an overview of security concepts, tools, and terminology.
Learn about the default set of Users, Groups, and Application roles by reading the summary in Section 2.1, "Working with the Default Users, Groups, and Application Roles".
Decide which authentication provider to use to authenticate users.
Set up the required users and groups.
Set up the required Application roles.
Assign each group to an appropriate Application role.
Fine tune the permissions that users and groups have in the Oracle BI repository (that is, the RPD file).
Fine tune the permissions that users and groups have in the Oracle BI Presentation Catalog.
If required, configure Single Sign-On (SSO).
If required, configure Secure Sockets Layer (SSL).
For a detailed list of setup steps, see Section 1.8, "Detailed List of Steps for Setting Up Security In Oracle Business Intelligence".
Oracle Business Intelligence 11g is tightly integrated with the Oracle Fusion Middleware Security architecture and delegates core security functionality to components of that architecture. Specifically, any Oracle Business Intelligence installation makes use of the following types of security providers:
An authentication provider that knows how to access information about the users and groups accessible to Oracle Business Intelligence and is responsible for authenticating users.
A policy store provider that provides access to Application roles and Application Policies, which forms a core part of the security policy and determines what users can and cannot see and do in Oracle Business Intelligence.
A credential store provider that is responsible for storing and providing access to credentials required by Oracle Business Intelligence.
By default, an Oracle Business Intelligence installation is configured with an authentication provider that uses the Oracle WebLogic Server embedded LDAP server for user and group information. The Oracle Business Intelligence default policy store provider and credential store provider store Credentials, Application roles and Application Policies in files in the domain.
After installing Oracle Business Intelligence you can reconfigure the domain to use alternative security providers, if desired. For example, you might want to reconfigure your installation to use an Oracle Internet Directory, Oracle Virtual Directory, Microsoft Active Directory, or another LDAP server for authentication. You might also decide to reconfigure your installation to use Oracle Internet Directory, rather than files, to store Credentials, Application roles, and Application Policies.
Several Oracle Business Intelligence legacy authentication options are still supported for backward compatibility. The best practice is to perform authentication and authorization using an identity store and authentication provider via the default security model described in this chapter. However, there are certain scenarios where this is not possible or where certain aspects of the legacy approach to authentication and authorization are required. Typically the use of these alternative methods requires that your user population and groups are not held in the Identity store referenced by the authentication provider configured in the Oracle WebLogic domain. Consequently, when using alternative authentication methods, several sections of this chapter are not relevant. Instead, refer to Appendix A, "Alternative Security Administration Options". Please note that Application roles described in this chapter are still used with alternative authentication and authorization mechanisms. Also note that the authentication provider configured in the Oracle WebLogic domain is always used by the BI System User, even when using alternative methods for other users.
Each Oracle Business Intelligence 11g installation has an associated Oracle WebLogic Server domain. Oracle Business Intelligence delegates user authentication to the first authentication provider configured for that domain.
The default authentication provider accesses user and group information stored in the LDAP server embedded in the Oracle Business Intelligence's Oracle WebLogic Server domain. The Oracle WebLogic Server Administration Console can be used to create and manage users and groups in the embedded LDAP server.
You might choose to configure an authentication provider for an alternative directory. In this case, Oracle WebLogic Server Administration Console enables you to view the users and groups in your directory. However, you need to continue to use the appropriate tools to make any modifications to the directory. For example, if you reconfigure Oracle Business Intelligence to use OID, you can view users and groups in Oracle WebLogic Server Administration Console but you must manage them in OID Console.
For more information about managing users and groups in the embedded LDAP server, see Chapter 2, "Managing Security Using the Default Security Configuration".
For more information about Oracle WebLogic Server domains and authentication providers, see Oracle Fusion Middleware Securing Oracle WebLogic Server.
You can continue to use the external table authentication method, instead of the default authentication provided with this release. For more information, see Appendix A, "Setting Up External Table Authentication".
After a user has been authenticated, the next critical aspect of security is ensuring that the user can do and see what they are authorized to do and see. Authorization for Oracle Business Intelligence Release 11g is controlled by a security policy defined in terms of Applications Roles.
Instead of defining the security policy in terms of users in groups in a directory server, Oracle Business Intelligence uses a role-based access control model. Security is defined in terms of Application roles that are assigned to directory server groups and users. For example, the default Application roles BIAdministrator, BIConsumer, and BIAuthor.
Application roles represent a functional role that a user has, which gives that user the privileges required to perform that role. For example, having the Sales Analyst Application role might grant a user access to view, edit and create reports on a company's sales pipeline.
This indirection between Application roles and directory server users and groups allows the administrator for Oracle Business Intelligence to define the Application roles and policies without creating additional users or groups in the corporate LDAP server. Instead, the administrator defines Application roles that meet the authorization requirements and assigns those roles to pre-existing users and groups in the corporate LDAP server.
In addition, the indirection afforded by Application roles allows the artifacts of a business intelligence system to be easily moved between development, test and production environments. No change to the security policy is needed and all that is required is to assign the Application roles to the users and groups available in the target environment.
The Figure 1-1 shows an example using the default set of users, groups, and Application roles.
Figure 1-1 shows the following:
The group named 'BIConsumers' contains User1, User2, and User3. Users in the group 'BIConsumers' are assigned the Application role 'BIConsumer', which enables the users to view reports.
The group named 'BIAuthors' contains User4 and User5. Users in the group 'BIAuthors' are assigned the Application role 'BIAuthor', which enables the users to create reports.
The group named 'BIAdministrators' contains User6 and User7. Users in the group 'BIAdministrators' are assigned the Application role 'BIAdministrator', which enables the users to manage responsibilities.
In Oracle Business Intelligence Release 11g, the security policy definition is split across the following components:
Presentation Services Catalog – This defines which catalog objects and Oracle BI Presentation Services functionality can be accessed by which users with specific Application roles. Access to functionality is defined in the Managing Privileges page in terms of Oracle BI Presentation Catalog privileges and access to Oracle BI Presentation Catalog objects is defined in the Permission dialog.
Repository – This defines which metadata items within the repository can be accessed by which Application roles and users. The Oracle BI Administration Tool is used to define this security policy.
Policy Store – This defines which Oracle BI Server, BI Publisher, and Real Time Decisions functionality can be accessed by given users or users with given Application roles. In the default Oracle Business Intelligence configuration, the policy store is managed using Oracle Enterprise Manager Fusion Middleware Control. For more information about the policy store, see Oracle Fusion Middleware Application Security Guide.
To find out about using these components, see Section 1.7, "Example: Looking at the Installed Users, Groups, and Application Roles".
When you install Oracle Business Intelligence, there are a number of pre configured Users, Groups, and Application roles that you can use to deploy Oracle Business Intelligence (for more information, see Section 2.1, "Working with the Default Users, Groups, and Application Roles").
To configure security in Oracle Business Intelligence, you use the following tools:
Note:
To see an example of using the Oracle Business Intelligence tools to configure the installed Users, Groups, and Application roles, see Section 2.2, "An Example Security Setup Using the Default Groups and Application Roles".The figure below summarizes the tools used to configure security in a default installation Oracle Business Intelligence using the embedded WebLogic LDAP Server.
You use Oracle WebLogic Server Administration Console to manage the embedded directory server that is used to authenticate users and groups.
The example screen shot below shows the users and groups\Users page in Oracle WebLogic Server Administration Console displaying a list of users in Oracle Business Intelligence.
Note: If you use Oracle Internet Directory as the authentication provider instead of the default the embedded WebLogic LDAP Server, then you use OID Console to manage users and groups.
You use Oracle Fusion Middleware Control to create and manage the Application roles and Application Policies that control access to Oracle Business Intelligence resources.
The example screen shot below shows the Application roles page in Fusion Middleware Control displaying the default Application roles named BIAdministrator, BIAuthor, and BIConsumer.
You use the Oracle BI Administration Tool to configure privileges in the metadata repository (that is, the RPD file).
The screenshot below shows the Identity Manager dialog, which enables you to manage users and Application roles.
This example takes a closer look at the installed Users, Groups, and Application roles using the Oracle Business Intelligence tools. Follow the steps in this section to learn how to use the Oracle Business Intelligence tools to configure security options.
To display installed objects in Oracle WebLogic Server Administration Console:
Log in to Oracle WebLogic Server Administration Console.
In the Domain Structure tab at the left-hand side, select the Security Realms link.
In the list of Realms, select the realm that you are configuring.
For example, myrealm.
Use the tabs and options on the Settings for <Realm name> dialog to configure users and groups.
For example, display the users and groups tab to edit users and groups. In the example screenshot below, you can see the installed groups named BIAdministrators, BIAuthors, and BIConsumers.
To display installed objects in Fusion Middleware Control:
Log in to Fusion Middleware Control.
From the Home page, select the Business Intelligence link.
Select the coreapplication link.
Display the Security tab.
Select the Configure and Manage Application Roles link.
In the example screenshot below, you can see the installed Application roles BIAdministrator, BIAuthor, and BIConsumer.
To display installed objects in the Administration Tool:
Log in to the Administration Tool.
Note: If you log in to the Administration Tool in online mode, then you can view all users from the WebLogic Server. If you log in to the Administration Tool in offline mode, then you can only view users that are stored in the repository.
Choose Manage, then Identity to display the Identity Manager dialog.
In the example screenshot below you can see the installed Application roles BIAdministrator, BIAuthor, and BIConsumer.
If you double-click the Application role named 'Sales Admin' to display the Application role <Name> dialog, then click Permissions, you can use the Object Permissions tab to set (in the repository) the Read and Write permissions for that Application role, in relation to objects and folders in the Oracle BI Presentation Catalog.
Close Identity Manager.
In the Presentation pane, expand the Paint folder, then right-click Markets to display the Presentation Table <Table name> dialog.
Click Permissions to display the Permissions <Table name> dialog.
In the example screenshot below, you can see the installed Application roles BIAdministrator, BIAuthor, and BIConsumer, and the radio buttons Read, Read/Write, No Access, and Default that are used to set the permissions for the Application roles.
To display installed objects in Administration Page in Oracle BI Presentation Catalog:
Log in to BI EE with Administrator privileges.
Select the Administration link to display the Administration page.
Select the Manage Privileges link.
In the example screenshot below, you can see the installed Application roles BIAdministrator, BIAuthor, and BIConsumer listed against each of the privileges that they have been assigned.
Select the BIAuthor link in the 'Access to KPI Builder' row, to display the Privilege <Privilege name> dialog.
Click the Add users/roles icon (+) to display the Add Application roles, Catalog Groups, and Users dialog.
In the example screenshot below you can see the installed Application roles BIAdministrator, BIAuthor, and BIConsumer, which can be assigned to this privilege.
This section explains how to set up security in a new installation of Oracle Business Intelligence. Some tasks are mandatory, some are optional, and some are conditionally required depending on the configuration choices that you make. You might also refer to this section if you are maintaining an existing installation of Oracle Business Intelligence.
After you have installed Oracle Business Intelligence, you typically evaluate the product using the default pre configured Users, Groups, and Application roles. Later, you typically create and develop your own Users, Groups, and Application roles iteratively to meet your business requirements.
After you have installed Oracle Business Intelligence, Oracle recommends that you complete these tasks in the order listed below.
Read this chapter 'Introduction to Security in Oracle Business Intelligence' to get an overview of security concepts, tools, and terminology. In particular, you should familiarize yourself with the Oracle Business Intelligence components and tools for configuring security by reading Section 1.6, "What Tools Configure Security in Oracle Business Intelligence?"
Learn about the default set of Users, Groups, and Application roles by reading the summary in Section 2.1, "Working with the Default Users, Groups, and Application Roles".
Decide which authentication provider to use to authenticate users, as follows:
If you want to use the default embedded WebLogic LDAP Server, then follow the tasks listed in Step 4 below.
If you want to reconfigure Oracle Business Intelligence to use a commercial authentication provider such as Oracle Internet Directory, then follow the tasks listed in Step 5 below.
Tip:
Oracle does not recommend using WebLogic Embedded LDAP Server in an environment with more than 1000 users. If you require a production environment with high-availability and scalability, then you should use a commercial directory server such as Oracle Internet Directory (OID) or a third-party directory server.For information about where to find the full list of supported authentication providers, see "System Requirements and Certification".
(Embedded WebLogic LDAP Server-specific) If you are using the default embedded WebLogic LDAP Server as the authentication provider, do the following:
Tip:
The simplest way to set up security is to create users and assign them to the default groups (that is, BIConsumers, BIAuthors, and BIAdministrators). For detailed steps, see Section 2.3.1.1, "Assigning a User to a Default Group".If you want to build a more complex security model using your own groups, create new groups and/or new Application roles, then assign your users to the new groups. For detailed steps, see Section 2.3.1.2, "Assigning a User to a New Group and a New Application Role".
Note:
If you have upgraded to this release from 10g, and want to authenticate users using the authentication provider configured for the Oracle WebLogic domain, you should review any RPD initialization blocks that set the USER system session variable. Setting the USER session variable is an alternative authentication mechanism that will be used to authenticate users attempting to access the BI Server if they fail authentication using the authentication provider configured for the Oracle WebLogic domain. For more information about working with RPDs, see Appendix A, "Defining a USER Session Variable for LDAP Authentication" and Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.Set up the users that you want to deploy as described in Section 2.3.3, "Creating a New User in the Embedded WebLogic LDAP Server".
For example, if you want to deploy Oracle Business Intelligence to 20 people who need to view analyses, you might create 20 users.
If you want to assign users to the default groups, (that is, BIConsumers, BIAuthors, and BIAdministrators), then follow the steps in Section 2.3.1.1, "Assigning a User to a Default Group".
For example, you might assign a set of users to the group named BIConsumers, a set of users to the group named BIAuthors, and a set of users to the group named BIAdministrators.
If you want to create new groups, set up the groups that you want to use as described in Section 2.3.4, "Creating a Group in the Embedded WebLogic LDAP Server".
For example, you might use the pre configured group named BIConsumers, or you might create your own group with similar privileges.
Assign your users to appropriate groups, as described in Section 2.3.5, "Assigning a User to a Group in the Embedded WebLogic LDAP Server".
For example, you might assign users to the pre configured group named BIConsumers, or you might assign users to a new group that you have created.
(Oracle Internet Directory (OID) specific) If you are using OID as the authentication provider, do the following:
Configure OID as the authentication provider as described in Section 3.2.1, "High Level Steps for Configuring Alternative Authentication Providers".
(Optional) Configure OID as the Credential Store and Policy Store Provider as described in Section 3.3, "Configuring OID as the Policy Store and Credential Store".
Use your authentication provider tools (for example, OID Console) to create your users and groups as required.
Set up the Application roles that you want to deploy as described in Section 2.4.2, "Creating Application Roles Using Fusion Middleware Control".
For example, you might use the default Application roles named BIConsumer, BIAuthor, and BIAdministrator, or you might create your own Application roles.
(Optional) If you do not want to use the pre configured Application Policies, set up the Application Policies that you want to deploy as described in Section 2.4.3, "Creating Application Policies Using Fusion Middleware Control".
For example, you might use the default Application Policies that are used by the default Application roles named BIConsumer, BIAuthor, and BIAdministrator, or you might create your own Application Policies.
Assign each group to an appropriate Application role, as follows:
If you are using the default groups (that is, BIConsumers, BIAuthors, and BIAdministrators) that are installed with the default embedded WebLogic LDAP Server, then these groups are assigned to an appropriate Application role (that is, BIConsumer, BIAuthor, or BIAdministrator). No additional steps are required to assign the default groups to Application roles.
If you have created new groups, you must assign the new groups to appropriate Application roles as described in Section 2.4.2.3, "Assigning a Group to an Application Role".
If you are using a commercial Authenticator Provider such as Oracle Internet Directory, then you must assign the groups to appropriate Application roles as described in Section 2.4.2.3, "Assigning a Group to an Application Role".
If you want to fine tune the permissions that users and groups have in the Oracle BI repository (that is, the RPD file), use the Administration Tool to update the permissions as described in Section 2.5, "Managing Metadata Repository Privileges Using the Oracle BI Administration Tool".
For example, you might want to enable an Application role called BISuperConsumer to create analyses, so you use the Administration Tool to change the 'Read' access to a subject area to 'Read/Write' access.
Note: If you are using the default SampleAppLite.rpd file in a production system, you should change the password from its installed value, using the Administration Tool (for more information about the SampleAppLite RPD file, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition).
If you want to fine tune the permissions that users and groups have in the Oracle BI Presentation Catalog, use the Administration Page in Analytics to change the permissions as described in Section 2.6, "Managing Presentation Services Catalog Privileges Using Application Roles".
For example, you might want to prevent an Application role called BISuperConsumer from viewing scorecards, so you use Administration Page in Analytics to change the Scorecard\View Scorecard privileges for BISuperConsumer from 'Granted' to 'Denied'.
If you want to deploy Single Sign-On, follow the steps in Chapter 4, "Enabling SSO Authentication".
Note: If you do not want to deploy Oracle Business Intelligence in a SSO environment, then no additional configuration steps are required to deploy the default configuration.
If you want to deploy secure sockets layer (SSL), follow the steps in Chapter 5, "SSL Configuration in Oracle Business Intelligence".
Oracle Business Intelligence is installed with SSL turned off. If you want to deploy Oracle Business Intelligence in an SSL environment, follow the steps in Chapter 5, "SSL Configuration in Oracle Business Intelligence".
Note: If you do not want to deploy Oracle Business Intelligence in an SSL environment, then no additional configuration steps are required to deploy the default configuration.
The Release 10g and Release 11g security models differ in the following ways:
Defining users and groups - In Oracle Business Intelligence Release 10g users and groups could be defined within a repository file using the Oracle BI Administration Tool. In Oracle Business Intelligence Release 11g users and groups can no longer be defined within a repository. The Oracle Business Intelligence Enterprise Edition Upgrade Assistant migrates users and groups from a Release 10g repository into the embedded LDAP server in a Release 11g installation.
Defining security policies – In Oracle Business Intelligence Release 10g security policies in the Oracle BI Presentation Catalog and repository could be defined to reference groups within a directory. In Oracle Business Intelligence Release 11g a level of indirection is introduced whereby security policies are defined in terms of Application roles, which are in turn are assigned to users and groups in a directory. This indirection allows an Oracle Business Intelligence Release 11g system to be deployed without changes to the corporate directory and eases movement of artifacts between development, test and production environments.
Use of the Administrator user – In an Oracle Business Intelligence Release 10g installation, a special user named Administrator has full administrative permissions and is also used to establish trust between processes within that installation. In Oracle Business Intelligence Release 11g there is no special significance to the name Administrator and there can be one or more users who are authorized to undertake different sets of administrative functions. In Oracle Business Intelligence Release 11g the identity used to establish trust between processes in an installation is configurable and independent.
Repository encryption – in Oracle Business Intelligence Release 10g certain sensitive elements within a repository are encrypted. In Oracle Business Intelligence Release 11g the entire repository is encrypted using a key derived from a user supplied password.
Caution:
A Release 11g repository can only be opened with the password. There is no mechanism for recovering a lost password.The following aspects of the Oracle Business Intelligence Release 10g security model remain in Release 11g:
Oracle BI Server Initialization Blocks – Oracle BI Server in Release 11g continues to support the use of initialization blocks for authentication and authorization. In Release 10g Oracle BI Server falls back to use initialization blocks if a matching user cannot be found in the repository. In Release 11g Oracle Business Intelligence falls back to use initialization blocks if the user cannot be authenticated by the installation's configured authentication provider.
Presentation Services Catalog Groups – Oracle Business Intelligence Release 11g continues to support the definition of Catalog groups within the Presentation Services Catalog. These groups are only visible within Oracle BI Presentation Services. Oracle recommends that Oracle BI Presentation Catalog groups be used for backward compatibility only and that Application roles be used instead for new installations.
SA System Subject Area – Oracle Business Intelligence Release 11g supports the use of SA System Subject Area, in combination with Oracle BI Server initialization blocks, to access user, group and profile information stored in database tables.
For more information, see Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition.
The following terms are used throughout this guide:
Oracle Business Intelligence permissions are granted by its Application roles. In the default security configuration, each role conveys a predefined set of permissions. An Application Policy is a collection of Java EE and JAAS policies that are applicable to a specific application. The Application Policy is the mechanism that defines the permissions each Application role grants. Permission grants are managed in the Application Policy corresponding to an Application role.
Represents a role a user has when using Oracle Business Intelligence. Is also the container used by Oracle Business Intelligence to grant permissions to members of a role. Application roles are managed in the policy store provider.
The process of verifying identity by confirming the credentials presented during logon.
A security provider used to access user and group information and is responsible for authenticating users. Oracle Business Intelligence default authentication provider is Oracle WebLogic Server embedded directory server and is named DefaultAuthenticator.
The process of granting an authenticated user access to a resource in accordance to their assigned privileges.
A Catalog group is defined locally in Oracle BI Presentation Services and is used to grant privileges in the Oracle Business Intelligence user interface in addition to granting Oracle BI Presentation Catalog permissions.
An Oracle Business Intelligence credential store is a file used to securely store system credentials used by the software components. This file is automatically replicated across all machines in the installation.
The credential store is used to store and manage credentials securely that are used internally between Oracle Business Intelligence components. For example, SSL certificates are stored here.
A process that enables confidential communication by converting plaintext information (data) to unreadable text which can be read only with the use of a key. Secure Sockets Layer (SSL) enables secure communication over TCP/IP networks, such as Web applications communicating through the Internet.
A GUID is typically a 32-character hexadecimal string that is system-generated to form a unique identifier for an object. In Oracle Business Intelligence a GUID is used to refer to individual users and groups.
Impersonation is a feature used by Oracle Business Intelligence components to establish a session on behalf of a user without employing the user's password. For example, impersonation is used when Oracle BI Scheduler executes an Agent.
A logically related group of Oracle WebLogic Server resources that includes an instance known as the Administration Server. Domain resources are configured and managed in the Oracle WebLogic Server Administration Console. During installation an Oracle WebLogic Server domain is created and Oracle Business Intelligence is installed into that domain. For more information, see Section B.2.2, "Oracle WebLogic Server Domain".
An identity store contains user name, password, and group membership information. In Oracle Business Intelligence, the identity store is typically a directory server and is what an authentication provider accesses during the authentication process. For example, when a user name and password combination is entered at log in, the authentication provider searches the identity store to verify the credentials provided. Oracle Business Intelligence can be re configured to use alternative identity stores. For a complete list, see System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1. For more information, see System Requirements and Certification.
The policy store is the repository of system and application-specific policies. It holds the mapping definitions between the default Oracle Business Intelligence Application roles, permissions, users and groups all configured as part of installation. Oracle Business Intelligence permissions are granted by assigning users and groups from the identity store to Application roles and permission grants located in the policy store.
Contains the definition of Application roles, Application Policies, and the members assigned (Users, Groups, and Applications Roles) to Application roles. The default policy store is a file that is automatically replicated across all machines in an Oracle Business Intelligence installation. A policy store can be file-based or LDAP-based.
These rights grant Presentation Services object level access. They are stored in the Presentation Services Catalog and managed by Oracle BI Presentation Server.
These rights grant access to Oracle BI Presentation Catalog features. They are stored in the Presentation Services Catalog and managed by Oracle BI Presentation Server. These privileges are either granted or denied.
Provides secure communication links. Depending upon the options selected, SSL might provide a combination of encryption, authentication, and repudiation. For HTTP based links the secured protocol is known as HTTPS.
The security policy defines the collective group of access rights to Oracle Business Intelligence resources that an individual user or a particular Application role have been granted. Where the access rights are controlled is determined by which Oracle Business Intelligence component is responsible for managing the resource being requested. A user's security policy is the combination of permission and privilege grants governed by the following elements:
Presentation Services Catalog: defines which Oracle BI Presentation Catalog objects and Oracle BI Presentation Services functionality can be accessed by users. Access to this functionality is managed in Oracle Business Intelligence user interface. These permissions and privileges can be granted to individual users or by membership in corresponding Application roles.
Repository File: defines access to the specified metadata within the repository file. Access to this functionality is managed in the Oracle BI Administration Tool. These permissions and privileges can be granted to individual users or by membership in corresponding Application roles.
Policy Store: defines which Oracle Business Intelligence, Oracle BI Publisher, and Real Time Decisions functionality can be accessed. Access to this functionality is managed in Oracle Enterprise Manager Fusion Middleware Control. These permissions and privileges can be granted to individual users or by membership in corresponding Application roles.
During installation an Oracle WebLogic Server domain is created and Oracle Business Intelligence is installed into that domain. Security for an Oracle WebLogic Server domain is managed in its security realm. A security realm acts as a scoping mechanism. Each security realm consists of a set of configured security providers, users, groups, security roles, and security policies. Only one security realm can be active for the domain. Oracle Business Intelligence authentication is performed by the authentication provider configured for the default security realm for the WebLogic Server domain in which it is installed. Oracle WebLogic Server Administration Console is the Administration Tool for managing an Oracle WebLogic Server domain.
A method of authorization enabling a user to authenticate once and gain access to multiple software application during a single browser session.
A user is an entity that can be authenticated. A user can be a person, such as an application user, or a software entity, such as a client application. Every user is given a unique identifier within in the identity store.
Groups are organized collections of users that have something in common. A group is a static identifier that is assigned by a system administrator. Users organized into groups facilitate efficient security management. There are two types of groups: an LDAP group and a Catalog group. A Catalog group is used to support the existing user base in Presentation Services to grant privileges in the Oracle Business Intelligence user interface. Using Catalog groups is not considered a best practice and is available for backward compatibility in upgraded systems.
|
 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
