From the Domain Structure pane, click Security Realms. Open the Providers tab. Click New to create a provider.

30-22 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter Figure 30–11 Settings Pane

4. Open the Providers tab.

The Provider Settings display see Figure 30–12 . Figure 30–12 Settings Pane - Providers

5. Click New to create a provider.

The Create a New Authentication Provider pane displays see Figure 30–13 . Configuring Single Sign-on 30-23 Figure 30–13 Create a New Authentication Provider Pane 6. Enter a name for the new provider for example, OAM ID Asserter, select OAMIdentityAsserter as its type and click OK. 7. On the Providers tab, click the newly added provider. The Common Settings pane for the authenticator displays see Figure 30–14 . Figure 30–14 Common Settings Pane

8. Set the control flag to REQUIRED and check that OAM_REMOTE_USER and

ObSSOCookie is set for Active Types. 9. Click Save to save you settings. 30-24 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter

30.2.4.3 Configuring the Default Authenticator and Provider Order

After configuring the OAM identity asserter, ensure that the default authenticators control flag is set to SUFFICIENT and reorder the providers as shown below:

1. Navigate to the Provider Settings pane see

Figure 30–12 .

2. Open the Default Authenticator and check that the control flag is set to

SUFFICIENT.

3. Do the same for any providers other than the two you just created.

4. On the Settings Pane, reset the provider order to:

■ OAMIdentityAsserter REQUIRED ■ OracleInternetDirectoryAuthenticator SUFFICIENT ■ DefaultAuthenticator SUFFICIENT ■ DefaultIdentityAsserter

5. Continue by configuring WebCenter Spaces for single sign-on mode as described

in Section 30.2.6.1, Configuring WebCenter Spaces for SSO. Also be sure to perform any further service and component configurations that apply to your environment as described in Section 30.2.6, Additional Single Sign-on Configurations.

30.2.4.4 Adding an OAM Single Sign-on Provider

After checking that the default authenticator’s control flag is set correctly, and that the order of the providers is correct, add an OAM SSO provider and restart all servers as described below. 1. Connect to the WebLogic domain using WLST and run the following command: addOAMSSOProviderloginuri={app.context}adfAuthentication, logouturi=oamssologout.html 2. Restart all servers.

30.2.5 Installing and Configuring the Oracle HTTP Server

This step is common to both OAM 10g and OAM 11g, and should be performed after installing and configuring OAM, and before configuring the WebLogic domain. This section describes how to install and configure the Oracle HTTP server OHS.

1. If you do not have already have an OHS install youd like to use, install the Oracle

HTTP Server 11.1.1.4.0 using the instructions in the section on Installing Oracle Web Tier in the Oracle Fusion Middleware Installation Guide for Oracle Web Tier. If you do have an existing installation, you will need to apply a patch to bring it up to OHS 11.1.1.4.0 as described in Applying the Latest Oracle Fusion Middleware Patch Set in the Oracle Fusion Middleware Patching Guide.

2. Configure Web Tier OHS so that it forwards requests to the Oracle WebLogic

Server for WebCenter using the following example in mod_wl_ohs.conf. Make sure that the WebLogic port numbers match your configuration. For more information, see Installing and Configuring Oracle HTTP Server 11g Webgate for Note: This is required for OAM 11g, but is only required for OAM 10g if the logout URI has been explicitly configured.