Configuring SSO in an Oracle Access Manager Environment

Use this section to find further information about how to configure SSO in an Oracle Access Manager environment.

See Configuring Single Sign-On in Oracle Fusion Middleware in Securing Applications with Oracle Platform Security Services. See Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager.

See Configuring BI Publisher to Use Oracle Access Manager (OAM) Single Sign-On in Administrator's Guide for Oracle Business Intelligence Publisher.

After the Oracle Fusion Middleware environment is configured, in general the following must be done to configure Oracle Business Intelligence:

• Configure the SSO provider to protect the Oracle Business Intelligence URL entry points.

• Configure the web server to forward requests from Presentation Services to the SSO provider.

• Configure the new identity store as the main authentication source for the Oracle WebLogic Server domain in which Oracle Business Intelligence has been installed. See Configuring a New Authenticator for Oracle WebLogic Server.

• Configure the Oracle WebLogic Server domain in which Oracle Business Intelligence is installed to use an Oracle Access Manager asserter. See Configuring Oracle Access Manager as a New Identity Asserter for Oracle WebLogic Server.

• After configuration of the SSO environment is complete, enable SSO authentication for Oracle Business Intelligence. See Enabling SSO Authentication Using Fusion Middleware Control.

Configuring a New Authenticator for Oracle WebLogic Server

After installing Oracle Business Intelligence, the Oracle WebLogic Server embedded LDAP server is the default authentication source (identity store).

To use a new identity store, for example, OID, as the main authentication source, you must configure the Oracle WebLogic Server domain, where Oracle Business Intelligence is installed.

See Administering Security for Oracle WebLogic Server 12c (12.2.1) and Using Oracle WebLogic Server Administration Console.

See Setting the JAAS Control Flag Option.

1. Log in to Oracle WebLogic Server Administration Console and click Lock & Edit in the Change Center.

2. Select Security Realms from the left pane and click myrealm

   The default Security Realm is named myrealm.

3. Display the Providers tab, then display the Authentication sub-tab.
4. Click New to launch the Create a New Authentication Provider page.

   Complete the fields as follows:

   • Name: OID Provider, or a name of your choosing.
   • Type: OracleInternetDirectoryAuthenticator
   • Click OK to save the changes and display the authentication providers list updated with the new authentication provider.
5. Click the newly added authenticator in the authentication providers table.
6. Navigate to Settings, then select the Configuration\Common tab:
   • Select SUFFICIENT from the Control Flag list.
   • Click Save.
7. Display the Provider Specific tab and specify the following settings using appropriate values for your environment:

   Section Name	Field Name	Description
   Connection	Host	The LDAP host name. For example, <localhost>.
   Connection	Port	The LDAP host listening port number. For example, 6050.
   Connection	Principal	The distinguished name (DN) of the user that connects to the LDAP server. For example, cn=orcladmin.
   Connection	Credential	The password for the LDAP administrative user entered as the Principal.
   Users	User Base DN	The base distinguished name (DN) of the LDAP server tree that contains users. For example, use the same value as in Oracle Access Manager.
   Users	All Users Filter	The LDAP search filter. For example, (&(uid=*) (objectclass=person)). The asterisk (*) filters for all users. Click More Info... for details.
   Users	User From Name Filter	The LDAP search filter. Click More Info... for details.
   Users	User Name Attribute	The attribute that you want to use to authenticate (for example, cn, uid, or mail). Set as the default attribute for user name in the directory server. For example, uid. Note: The value that you specify here must match the User Name Attribute that you are using in the authentication provider, as described in the next task Configuring User Name Attributes.
   Groups	Group Base DN	The base distinguished name (DN) of the LDAP server tree that contains groups (same as User Base DN).
   General	GUID attribute	The attribute used to define object GUIDs in LDAP. orclguid Note: You should not change this default value, in most cases the default value here is sufficient.

8. Click Save.
9. Perform the following steps to set up the default authenticator for use with the Identity Asserter:
   1. At the main Settings for myrealm page, display the Providers tab, then display theAuthentication sub-tab, then select DefaultAuthenticator to display its configuration page.
   2. Display the Configuration\Common tab and select 'SUFFICIENT' from the Control Flag list.
   3. Click Save.
10. Perform the following steps to reorder Providers:
    1. Display the Providers tab.
    2. Click Reorder to display the Reorder Authentication Providers page
    3. Select a provider name and use the arrow buttons to order the list of providers as follows:
       • OID Authenticator (SUFFICIENT)
       • OAM Identity Asserter (REQUIRED)
       • Default Authenticator (SUFFICIENT)
    4. Click OK to save your changes.
11. In the Change Center, click Activate Changes.
12. Restart Oracle WebLogic Server.

Configuring Oracle Access Manager as a New Identity Asserter for Oracle WebLogic Server

The Oracle WebLogic Server domain in which Oracle Business Intelligence is installed must be configured to use an Oracle Access Manager asserter.

See Enabling Oracle Business Intelligence to Use SSO Authentication

1. Log in to Oracle WebLogic Server Administration Console.

2. In Oracle WebLogic Server Administration Console, select Security Realms from the left pane and click the realm you are configuring. For example, myrealm.

3. Select Providers.

4. Click New. Complete the fields as follows:
   • Name: OAM Provider, or a name of your choosing.
   • Type: OAMIdentityAsserter.
5. Click OK.
6. Click Save.
7. In the Providers tab, perform the following steps to reorder Providers:
   1. Click Reorder
   2. In the Reorder Authentication Providers page, select a provider name, and use the arrows beside the list to order the providers as follows:
      • OID Authenticator (SUFFICIENT)
      • OAM Identity Asserter (REQUIRED)
      • Default Authenticator (SUFFICIENT)
   3. Click OK to save your changes.
8. In the Change Center, click Activate Changes.
9. Restart Oracle WebLogic Server.

   You can verify that Oracle Internet Directory is the new identity store (default authenticator) by logging back into Oracle WebLogic Server and verifying the users and groups stored in the LDAP server appear in the console.

10. Enable SSO authentication.

    .