Testing the Oracle Access Manager Authenticator Implementation

16-64 Oracle Fusion Middleware Application Security Guide

16.6.3 Configuring Providers in a WebLogic Domain for Oracle Web Services Manager

To use Oracle Access Manager Identity Asserter with Oracle Web Services Manager protected Web services, several Authentication Providers must be configured and ordered in a WebLogic domain: ■ OAM Identity Asserter: REQUIRED ■ OID Authenticator: SUFFICIENT ■ DefaultAuthenticator: SUFFICIENT This procedure is nearly identical to the one for the Oracle Access Manager Identity Asserter. The difference in this case is that Oracle Web Services Manager requires a custom AccessGate and additional provider-specific values are required: ■ Primary Access Server: Specify the host and part. For example: abcd:7777 ■ Access Gate Name: The name of the AccessGate protecting the application. For example: mmmm ■ Access Gate Password: The AccessGate password as specified in the Access System Console. You can add these using either the Oracle WebLogic Administration Console or Oracle WebLogic Scripting Tool WLST command-line tool. To set up providers in a WebLogic domain 1. No Oracle Fusion Middleware Application : Obtain the Oracle Access Manager provider if you have no Oracle Fusion Middleware application. a. Log in to Oracle Technology Network at: http:www.oracle.comtechnologysoftwareproductsmiddlewareht docs111110_fmw.html b. Locate the oamAuthnProvider ZIP file with Access Manager WebGates 10.1.4.3.0. For example: oamAuthnProviderversion.zip c. Extract and copy the oamAuthnProvider.jar to the following path on the computer hosting Oracle WebLogic Server: BEA_HOMEwlserver_10.xserverlibmbeantypesoamAuthnProvider.jar 2. Log in to the Oracle WebLogic Administration Console.

3. OAM Identity Asserter

: Perform the following steps to add this provider: See Also: ■ About Oracle WebLogic Server Authentication and Identity Assertion Providers on page 16-41 ■ Oracle Fusion Middleware Oracle WebLogic Scripting Tool ■ Oracle Fusion Middleware WebLogic Scripting Tool Command Reference Note: With a Oracle Fusion Middleware application installed, you have the required provider file. Skip Step 1. Configuring Single Sign-On Using Oracle Access Manager 10g 16-65

a. Click Security Realms, Default Realm Name, and click Providers.

b. Click Authentication, click New, and then enter a name and select a type: Name: OAM Identity Asserter Type: OAMIdentityAsserter OK c. In the Authentication Providers table, click the newly added authenticator.

d. On the Common tab, set the Control Flag to REQUIRED, and click Save.

e. Click Platform-Specific tab and configure these parameters: Primary Access Server: Specify the host and part. For example: abcd:7777 Access Gate Name: The name of the AccessGate protecting the application. For example: mmmm Access Gate Password: The AccessGate password as specified in the Access System Console. Save

4. OID Authenticator

: Perform the following steps to add this provider.

a. Click Security Realms, Default Realm Name, and click Providers

b. Click New, enter a name, and select a type: Name: OID Authenticator Type: OracleInternetDirectoryAuthenticator Click OK. c. In the Authentication Providers table, click the newly added authenticator.

d. On the Settings page, click the Common tab, set the Control Flag to

SUFFICIENT , and then click Save.

e. Click the Provider Specific tab and specify the following required settings

using values for your own environment: Host: Your LDAP host. For example: localhost Port: Your LDAP host listening port. For example: 6050 Principal: LDAP administrative user. For example: cn=orcladmin Credential: LDAP administrative user password. User Base DN: Same searchbase as in Oracle Access Manager. All Users Filter: For example: uid=objectclass=person User Name Attribute: Set as the default attribute for username in the LDAP directory. For example: uid Group Base DN: The group searchbase same as User Base DN Click Save. Note: Do not set the All Groups filter as the default works fine as is.