11 Integration With Oracle Identity Management

This chapter describes how to integrate Oracle SOA Suite with Oracle Identity Management. It contains the following sections:

• Section 11.1, "Credential and Policy Store Configuration"

• Section 11.2, "Oracle Access Manager Integration"

• Section 11.3, "Backing Up the Installation"

11.1 Credential and Policy Store Configuration

The following topics describe credential and policy store configuration in detail:

• Section 11.1.1, "Overview of Credential and Policy Store Configuration"

• Section 11.1.2, "Credential Store Configuration"

• Section 11.1.3, "Policy Store Configuration"

• Section 11.1.4, "Reassociation of Credentials and Policies"

11.1.1 Overview of Credential and Policy Store Configuration

Oracle Fusion Middleware allows using different types of credential and policy stores in a WebLogic domain. Domains can use stores based on an XML file or on different types of LDAP providers. When a domain uses an LDAP store, all policy and credential data is kept and maintained in a centralized store. However, when using XML policy stores, the changes made on Managed Servers are not propagated to the Administration Server unless they use the same domain home. The Oracle Fusion Middleware SOA Suite EDG topology uses different domain homes for the Administration Server and the Managed Server, thus Oracle requires the use of an LDAP store as policy and credential store for integrity and consistency. By default Oracle WebLogic Server domains use an XML file for the policy store. The following sections describe the steps required to change the default store to Oracle Internet Directory LDAP for credentials or policies.

Note:

The backend repository for the policy store and the credential store must use the same kind of LDAP server. To preserve this coherence, note that reassociating one store implies reassociating the other one, that is, the re-association of both the credential and the policy stores is accomplished as a unit using the Fusion Middleware Control or the WLST command reassociateSecurityStore. For more information, see Section 11.1.4, "Reassociation of Credentials and Policies."

11.1.2 Credential Store Configuration

A credential store is a repository of security data (credentials). A credential can hold user name and password combinations, tickets, or public key certificates. Credentials are used during authentication, when principals are populated in subjects, and, further, during authorization, when determining what actions the subject can perform. In this section, steps are provided to configure Oracle Internet Directory LDAP as a credential store for the Oracle Fusion Middleware SOA Suite EDG topology. For more details on credential store configuration, refer to the "Configuring the Credential Store" chapter in the Oracle Fusion Middleware Security Guide.

The following section describe credential store configuration:

• Section 11.1.2.1, "Creating the LDAP Authenticator"

• Section 11.1.2.2, "Moving the WebLogic Administrator to LDAP"

• Section 11.1.2.3, "Reassociating the Domain Credential Store"

11.1.2.1 Creating the LDAP Authenticator

To be safe, before you create the LDAP authenticator, you should first back up the relevant configuration files:

ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/config.xml
ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/fmwconfig/jps-config.xml
ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/fmwconfig/system-jazn-data.xml

Also back up the boot.properties file for the Administration Server.

To configure the credential store to use LDAP, set the proper authenticator using the WebLogic Server Console:

1. Log in to the WebLogic Server Console.

2. Click the Security Realms link on the left navigational bar.

3. Click the myrealm default realm entry to configure it.

4. Open the Providers tab within the realm.

5. Observe that there is a DefaultAuthenticator provider configured for the realm.

6. Click Lock and Edit.

7. Click the New button to add a new provider.

8. Enter a name for the provider such as OIDAuthenticator or OVDAuthenticator depending on whether Oracle Internet Directory or Oracle Virtual Directory will be used.

9. Select the OracleInternetDirectoryAuthenticator or OracleVirtualDirectoryAuthenticator type from the list of authenticators depending on whether Oracle Internet Directory or Oracle Virtual Directory will be used.

10. Click OK.

11. In the Providers screen, click the newly created Authenticator.

12. Set the control flag to SUFFICIENT. This indicates that if a user can be authenticated successfully by this authenticator, then it should accept that authentication and should not continue to invoke any additional authenticators. If the authentication fails, it will fall through to the next authenticator in the chain. Make sure all subsequent authenticators also have their control flag set to SUFFICIENT; in particular, check the DefaultAuthenticator and set that to SUFFICIENT.

13. Click Save to save this setting.

14. Open the Provider Specific tab to enter the details for the LDAP server.

15. Enter the details specific to your LDAP server, as shown in the following table:

    Parameter	Value	Value Description
    Host	For example: oid.mycompany.com	The LDAP server's server ID.
    Port	For example: 636	The LDAP server's port number.
    Principal	For example: cn=orcladmin	The LDAP user DN used to connect to the LDAP server.
    Credential	NA	The password used to connect to the LDAP server
    SSL Enabled	Checked	Specifies whether SSL protocol is used when connecting to LDAP server.
    User Base DN	For example: cn=users,dc=us,dc=mycompany,dc=com	Specify the DN under which your Users start.
    Group Base DN	For example: cn=groups,dc=us,dc=mycompany,dc=com	Specify the DN that points to your Groups node.
    Use Retrieved User Name as Principal	Checked	Must be turned on.

    
    

    Click Save when done.

16. Click Activate Changes to propagate the changes.

11.1.2.1.1 Setting the Order of Providers

Reorder the OID/OVD Authenticator and Default Authenticator and ensure that the control flag for each authenticator is set as follows:

• OID LDAP Authenticator: SUFFICIENT

• Default Authenticator: SUFFICIENT

Restart the Administration Server using the procedure in Section 4.7, "Starting the Administration Server on SOAHOST1."

11.1.2.2 Moving the WebLogic Administrator to LDAP

This section provides details for provisioning a new administrator user and group for managing the Oracle Fusion Middleware SOA Suite EDG WebLogic Domain. This section describes the following tasks:

• Section 11.1.2.2.1, "Provisioning Admin Users and Groups in an LDAP Directory"

• Section 11.1.2.2.2, "Assigning the Admin Role to the Admin Group"

• Section 11.1.2.2.3, "Updating the boot.properties File and Restarting the System"

11.1.2.2.1 Provisioning Admin Users and Groups in an LDAP Directory

As mentioned in the introduction to this section, users and groups from multiple WebLogic domains may be provisioned in a central LDAP user store. In such a case, there is a possibility that one WebLogic admin user may have access to all the domains within an enterprise. This is not a desirable situation. To avoid this, the users and groups provisioned must have a unique distinguished name within the directory tree. In this guide, the admin user and group for the SOA EDG WebLogic domain will be provisioned with the DNs below:

• Admin User DN:

  cn=weblogic_soa,cn=Users,dc=us,dc=mycompany,dc=com
  

• Admin Group DN:

  cn=SOA Administrators,cn=Groups,dc=us,dc=mycompany,dc=com
  

Follow these steps to provision the admin user and admin group in Oracle Internet Directory:

1. Create an ldif file named admin_user.ldif with the contents shown below and then save the file:

   dn: cn=weblogic_soa, cn=Users, dc=us, dc=mycompany, dc=com
   orclsamaccountname: weblogic_soa
   givenname: weblogic_soa
   sn: weblogic_soa
   userpassword: Welcome1
   obver: 10.1.4.0
   mail: weblogic_soa
   objectclass: top
   objectclass: person
   objectclass: organizationalPerson
   objectclass: inetorgperson
   objectclass: orcluser
   objectclass: orcluserV2
   objectclass: oblixorgperson
   uid: weblogic_soa
   cn: weblogic_soa
   description: Admin User for the SOA Domain
   

2. Run the ldapadd command located under the ORACLE_HOME/bin directory to provision the user in Oracle Internet Directory.

   Note:

   The ORACLE_HOME used here is the ORACLE_HOME for the Identity Management installation where Oracle Internet Directory resides. The ORACLE_HOME environment variable must be set for the ldapadd command to succeed.

   For example (the command is shown as two lines in the example below for readability purposes, but you should enter the command on a single line):

   OIDHOST1> ORACLE_HOME/bin/ldapadd -h oid.mycompany.com -p 389 -D
   cn="orcladmin" -w welcome1 -c -v -f admin_user.ldif
   

3. Create an ldif file named admin_group.ldif with the contents shown below and then save the file:

   dn: cn=SOA Administrators, cn=Groups, dc=us, dc=mycompany, dc=com
   displayname: SOA Administrators
   objectclass: top
   objectclass: groupOfUniqueNames
   objectclass: orclGroup
   uniquemember: cn=weblogic_soa,cn=users,dc=us,dc=mycompany,dc=com
   cn: SOA Administrators
   description: Administrators Group for the SOA Domain
   

4. Run the ldapadd command located under the ORACLE_HOME/bin/ directory to provision the group in Oracle Internet Directory (the command is shown as two lines in the example below for readability purposes, but you should enter the command on a single line):

   OIDHOST1> ORACLE_HOME/bin/ldapadd -h oid.mycompany.com -p 389 -D
   cn="orcladmin" -w welcome1 -c -v -f admin_group.ldif
   

11.1.2.2.2 Assigning the Admin Role to the Admin Group

After adding the users and groups to Oracle Internet Directory, the group must be assigned the Admin role within the WebLogic domain security realm. This enables all users that belong to the group to be administrators for that domain. Follow these steps to assign the Admin role to the Admin group:

1. Log into the WebLogic Administration Server Console.

2. In the left pane of the console, click Security Realms.

3. On the Summary of Security Realms page, click myrealm under the Realms table.

4. On the Settings page for myrealm, click the Roles & Policies tab.

5. On the Realm Roles page, expand the Global Roles entry under the Roles table. This brings up the entry for Roles. Click on the Roles link to bring up the Global Roles page.

6. On the Global Roles page, click the Admin Role to bring up the Edit Global Role page:

   1. On the Edit Global Roles page, under the Role Conditions table, click the Add Conditions button.

   2. On the Choose a Predicate page, select Group from the drop down list for predicates and click Next.

   3. On the Edit Arguments Page, specify SOA Administrators in the Group Argument field and click Add.

7. Click Finish to return to the Edit Global Rule page.

8. The Role Conditions table now shows the SOA Administrators Group as an entry.

9. Click Save to finish adding the Admin Role to the SOA Administrators Group.

10. Validate that the changes were successful by bringing up the WebLogic Administration Server Console using a web browser. Log in using the credentials for the weblogic_soa user.

    Note:

    Each SOA application has its own predefined roles and groups defined for administration and monitoring. By default, the "Administrator" group allows these operations. However, the "Administrator" group may be too broad. For example, you may not want B2B Administrators to be Weblogic Server Domain Administrators where SOA is running. Therefore, you may wish to create a a more specific group, such as "SOA Administrators." In order for the different applications to allow the SOA Administrator group to administer the different systems, you must add the required roles to the SOA Administrator group. For example, for B2B's Administration, add the B2BAdmin role to the SOA Administrators group, for Worklistapp's administration, add the SOAAdmin role. Refer to each component's specific roles for the required roles in each case.

11.1.2.2.3 Updating the boot.properties File and Restarting the System

The boot.properties file for the Administration Server should be updated with the WebLogic admin user created in Oracle Internet Directory. Follow the steps below to update the boot.properties file:

1. On SOAHOST1, go the following directory:

   SOAHOST1>cd ORACLE_BASE/admin/domainName/aserver/domainName/servers/
   AdminServer/security
   

2. Rename the existing boot.properties file:

   SOAHOST1> mv boot.properties boot.properties.backup
   

3. Use a text editor to create a file called boot.properties under the security directory. Enter the following lines in the file:

   username=adminUser
   password=adminUserPassword
   

4. Save the file.

5. Stop the Administration Server:

   SOAHOST1> cd ORACLE_BASE/admin/domainName/aserver/domainName/bin
   SOAHOST1> ./stopWebLogic.sh
   

6. Start the Administrator Server using the procedure in Section 4.7, "Starting the Administration Server on SOAHOST1."

11.1.2.3 Reassociating the Domain Credential Store

The re-association of both the Credential and the Policy stores is accomplished as a unit using Fusion Middleware Control or the WLST command reassociateSecurityStore. See Section 11.1.4, "Reassociation of Credentials and Policies" for detailed steps

11.1.3 Policy Store Configuration

The domain policy store is the repository of system and application-specific policies. In a given domain, there is one store that stores all policies that all applications deployed in the domain may use. This section provides the steps to configure Oracle Internet Directory LDAP as the policy store for the Oracle Fusion Middleware SOA Suite EDG topology. For more details on policy store configuration, refer to the "OPSS Authorization and the Policy Store" chapter in the Oracle Fusion Middleware Security Guide. Oracle Fusion Middleware Security Guide.

11.1.3.1 Prerequisites to Using an LDAP-Based Policy Store

In order to ensure the proper access to an LDAP server directory (Oracle Internet Directory) used as a policy store, you must set a node in the server directory.

An Oracle Internet Directory administrator must follow these steps to create the appropriate node in an Oracle Internet Directory Server:

1. Create an LDIF file (assumed to be jpstestnode.ldif in this example) specifying the following DN and CN entries:

   dn: cn=jpsroot_soa
   cn: jpsroot_soa
   objectclass: top
   objectclass: OrclContainer
   

   The distinguished name of the root node (illustrated by the string jpsroot_soa above) must be distinct from any other distinguished name. One root node can be shared by multiple WebLogic domains. It is not required that this node be created at the top level, as long as read and write access to the subtree is granted to the Oracle Internet Directory administrator.

2. Import this data into Oracle Internet Directory server using the command ldapadd, as illustrated in the following example (the command is shown as two lines in the example below for readability purposes, but you should enter the command on a single line):

   OIDHOST1> ORACLE_HOME/bin/ldapadd -h ldap_host -p ldap_port -D
   cn=orcladmin -w password -c -v -f jpstestnode.ldif
   

3. Verify that the node has been successfully inserted using the command ldapsearch, as illustrated in the following example (the command is shown as two lines in the example below for readability purposes, but you should enter the command on a single line):

   OIDHOST1> ORACLE_HOME/bin/ldapsearch -h ldap_host -p ldap_port -D
   cn=orcladmin -w password -b "cn=jpsroot_soa" objectclass="orclContainer"
   

4. When using Oracle internet Directory as the LDAP-Based Policy Store run the utility oidstats.sql in the INFRADBHOSTs to generate database statistics for optimal database performance:

   OIDHOSTn> ORACLE_HOME/ldap/admin/oidstats.sql
   

   The oidstats.sql utility must be run just once after the initial provisioning. For details about this utility, consult the Oracle Fusion Middleware User Reference for Oracle Identity Management.

11.1.3.2 Cataloging Oracle Internet Directory Attributes

An Oracle Internet Directory attribute used in a search filter must be indexed. The command ldapmodify, whose syntax is illustrated below, can also be used to index attributes specified in an LDIF file (the command is shown as two lines in the example below for readability purposes, but you should enter the command on a single line):

OIDHOST1> ORACLE_HOME/bin/ldapmodify -h host -p port -D bindDN -w
bindPassword -v -f catalogue-modify-ldif-filename

For example, the above command can be used with the following sample LDIF file to catalog the attributes createtimestamp and modifytimestamp:

dn: cn=catalogs
changetype: modify
add: orclindexedattribute
orclindexedattribute: modifytimestamp
orclindexedattribute: createtimestamp

Each of the following Oracle Internet Directory attributes must be indexed:

orclrolescope
orclassignedroles
orclApplicationCommonName
orclAppFullName
orclCSFAlias
orclCSFKey
orclCSFName
orclCSFDBUrl
orclCSFDBPort
orclCSFCredentialType
orclCSFExpiryTime
modifytimestamp
createtimestamp
orcljpsassignee

11.1.3.3 Reassociating the Domain Policy Store

Reassociating the policy store consists in migrating policy data from a file- or LDAP-based repository to an LDAP-based repository, that is, re-association changes the repository preserving the integrity of the data stored. For each policy in the source policy store, re-association searches the target LDAP directory and, if it finds a match, it updates the matching policy as appropriate. If none is found, it simply migrates the policy as is.

At any time, after a domain policy store has been instantiated, a file- or LDAP-based policy store can be reassociated into an LDAP-based policy store storing the same data. To support it, the domain has to be configured, as appropriate, to use an LDAP policy store.

The re-association of both the credential and the policy stores is accomplished as a unit using Fusion Middleware Control or the WLST command reassociateSecurityStore. See Section 11.1.4, "Reassociation of Credentials and Policies" for detailed steps.

11.1.4 Reassociation of Credentials and Policies

To reassociate the policy and credential store with Oracle Internet Directory, use the WLST reassociateSecurityStore command. Follow these steps:

1. From SOAHOST1, start the wlst shell:

   SOAHOST1>cd ORACLE_COMMONHOME/common/bin
   SOAHOST1>./wlst.sh
   

2. Connect to the WebLogic Administration Server using the wlst connect command shown below:

   Syntax:

   connect('AdminUser',"AdminUserPassword",t3://hostname:port)
   

   For example:

   connect("weblogic","welcome1","t3://ADMINVHN:7001")
   

3. Run the reassociateSecurityStore command as shown below:

   Syntax:

   reassociateSecurityStore(domain="domainName",admin="cn=orcladmin",
   password="orclPassword",ldapurl="ldap://LDAPHOST:LDAPPORT",servertype="OID",
   jpsroot="cn=jpsroot_soa")
   

   For example:

   wls:/SOAEDGDomain/serverConfig>reassociateSecurityStore(domain="soaedg_domain",
   admin="cn=orcladmin",password="welcome1",ldapurl="ldap://oid.mycompany.com:389",servertype="OID",jpsroot="cn=jpsroot_soa")
   

   The output for the command is shown below:

   {servertype=OID,jpsroot_soa=cn=jpsroot_soa_idm_idmhost1,admin=cn=orcladmin,
   domain=IDMDomain,ldapurl=ldap://oid.mycompany.com:389,password=welcome1}
   Location changed to domainRuntime tree. This is a read-only tree with
   DomainMBean as the root.
   
   For more help, use help(domainRuntime)
   
   Starting Policy Store reassociation.
   LDAP server and  ServiceConfigurator setup done.
   
   Schema is seeded into LDAP server
   Data is migrated to LDAP server
   Service in LDAP server after migration has been tested to be available
   Update of jps configuration is done
   Policy Store reassociation done.
   Starting credential Store reassociation
   LDAP server and  ServiceConfigurator setup done.
   Schema is seeded into LDAP server
   Data is migrated to LDAP server
   Service in LDAP server after migration has been tested to be available
   Update of jps configuration is done
   Credential Store reassociation done
   Jps Configuration has been changed. Please restart the server.
   

4. Restart the Administration Server after the command completes successfully.

   To restart the Administration Server, use the procedure in Section 4.7, "Starting the Administration Server on SOAHOST1."

   Note:

   For credential and policy changes to take effect, the servers in the domain must be restarted.

11.2 Oracle Access Manager Integration

This section describes how to set up Oracle Access Manager as the single sign-on solution for the Oracle SOA Suite EDG topology.

11.2.1 Overview of Oracle Access Manager Integration

Oracle Access Manager (OAM) is the recommended single sign-on solution for Oracle Fusion Middleware 11g Release 1. For more information on installing and configuring an OAM installation, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management. This chapter explains the procedure for configuring the SOA installation with an existing OAM installation and the underlying directory service. Oracle recommends using either Oracle Internet Directory (OID) or Oracle Virtual Directory (OVD) or both of these directory services.

Note:

The SOA EDG topology described in this book uses a Single Sign-On configuration where both the SOA System and the Single Sign-On System are in the same network domain (mycompany.com) For a multi-domain configuration, please refer to the required configuration steps in "Chapter 7, Configuring Single Sign-On," of the Oracle Access Manager Access Administration Guide.

11.2.2 Prerequisites for Oracle Access Manager

The setup for Oracle Access Manager (OAM) assumes an existing OAM installation complete with Access Managers and a policy protecting the Policy Manager. For more information on installing and configuring an OAM installation, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management. This setup includes a directory service such as Oracle Internet Directory (OID) either as a stand-alone or as part of an Oracle Virtual Directory (OVD) configuration. This chapter will provide the necessary steps for configuring your SOA installation with either OID or OVD.

In addition, the OAM installation should have its own Web server configured with WebGate. This section also provides the steps for using the OAM Web server as a delegated authentication server.

11.2.3 Using the OAM Configuration Tool

The OAM Configuration Tool (oamcfg) starts a series of scripts and setup the required policies. It requires various parameters as inputs. Specifically, it creates the following:

1. A Form Authentication scheme in OAM

2. Policies to enable authentication in WebLogic Server

3. A WebGate entry in OAM to enable Oracle HTTP Server WebGates (from your Web Tier) to protect your configured application

4. A Host Identifier, depending on the scenario chosen (a default host identifier would be used, if not provided)

5. Policies to protect and unprotect application specific URLs.

This section covers the following topics:

• Section 11.2.3.1, "Collecting the Information for the OAM Configuration Tool"

• Section 11.2.3.2, "Running the OAM Configuration Tool"

• Section 11.2.3.3, "Verifying Successful Creation of the Policy Domain and AccessGate"

• Section 11.2.3.4, "Updating the Host Identifier"

• Section 11.2.3.5, "Updating the WebGate Profile"

• Section 11.2.3.6, "Adding Additional Access Servers"

• Section 11.2.3.7, "Configuring Delegated Form Authentication"

11.2.3.1 Collecting the Information for the OAM Configuration Tool

The following information should be collected or prepared prior to running the OAM Configuration tool:

1. Password: Create a secure password. This will be used as the password for the WebGate installation created later.

2. LDAP Host: host name of the Directory Server or Load Balancer address in the case of an HA/EDG configuration.

3. LDAP Port: port of the Directory Server.

4. LDAP USER DN: DN of the LDAP admin user. This will be a value such as "cn=orcladmin."

5. LDAP password: password of the LDAP admin user

6. oam_aa_host: host name of an Oracle Access Manager

7. oam_aa_port: port of the Oracle Access Manager

11.2.3.2 Running the OAM Configuration Tool

The OAM Configuration Tool resides in the ORACLE_COMMON_HOME/modules/oracle.oamprovider_11.1.1/ directory (ORACLE_COMMON_HOME depends on which machine you are running the configuration tool). The tool can be run from any machine with the required installation files. In this case, we run it from SOAHOST1.

The OAM Configuration Tool should be run as follows (all on a single command line):

MW_HOME/jrockit_160_<version>/bin/java -jar oamcfgtool.jar mode=CREATE
app_domain="SOA_EDG"
protected_uris="$URI_LIST"
app_agent_password=<Password_to_be_provisioned_for_App_Agent>
ldap_host=OID.MYCOMPANY.COM
ldap_port=389
ldap_userdn="cn=orcladmin"
ldap_userpassword=<Password_of_LDAP_Admin_User>
oam_aa_host=OAMHOST1
oam_aa_port=OAMPORT1

The $URI_LIST variable in the above command depends on the topology:

• SOA only:

  $URI_LIST="/DefaultToDoTaskFlow,/integration/worklistapp, /b2b,/sdpmessaging/userprefs-ui,/em,/soa/composer,/console,/b2bconsole, /bpm/composer (For BPM systems only),/bpm/workspace (For BPM systems only)"

• BAM only:

  $URI_LIST="/OracleBAM,/sdpmessaging/userprefs-ui,/em,/console to current /OracleBAM"

• SOA and BAM:

  $URI_LIST="/DefaultToDoTaskFlow,/integration/worklistapp, /b2b,/sdpmessaging/userprefs-ui,/em,/console,/OracleBAM,/b2bconsole,/bpm/composer (FOR BPM Systems only),/bpm/workspace (For BPM systems only)"

Note:

If BAM is installed later or other additional URLs need to be protected, the OAM configuration tool should be executed again using the same app_domain and including all the URLs that would be protected (not just the new ones).

If your command ran successfully, you should see the following output:

Processed input parameters
Initialized Global Configuration
Successfully completed the Create operation
Operation Summary:
Policy Domain: SOA_EDG
Host Identifier: SOA_EDG
Access Gate ID: SOA_EDG_AG

11.2.3.3 Verifying Successful Creation of the Policy Domain and AccessGate

Verifying the Policy Domain

To verify the policy domain, complete these steps:

1. Log on to the Oracle Access Manager: http://OAMADMINHOST:<port>/access/oblix/

2. Click Policy Manager.

3. Click the My Policy Domains link on the left panel, you will see a list of all policy domains, among which the domain you just created will be listed. It will have the suffix _PD (for example, SOA_EDG_PD ). In the third column (URL prefixes, you will also see the URIs you specified during the creation of this domain).

4. Click the link to the policy domain you just created. you will land in the General area of this domain.

5. Click the Resources tab, you will see the URIs you specified. You can also click other tabs to view other settings.

Verifying the AccessGate Configuration

To verify the AccessGate configuration, complete these steps:

1. Click the Access System Console link on the top right hand side (this acts like a toggle; after you click it, it becomes the Policy Manager link).

2. Click the Access System Configuration tab.

3. Click the AccessGate Configuration link on the left panel.

4. Enter 'SOA_EDG' as the search criterion (or any other substring you may have used as the app_domain name in Section 11.2.3.2, "Running the OAM Configuration Tool"), and click Go.

5. Once the AccessGate for the domain you just created shows up (this will have the suffix _AG (for example, SOA_EDG_AG), click it, you will see the details of the AccessGate which you just created.

11.2.3.4 Updating the Host Identifier

The OAM Configuration Tool uses the value of the app_domain parameter to create a host identifier for the policy domain. This host identifier must be updated with all the host name variations for the host so that the configuration works correctly. Follow the steps below to update the host identifier created by the OAM Configuration Tool:

1. Navigate to the Access System Console by specifying the following URL in your web browser:

   http://hostname:port/access/oblix
   

   where hostname refers to the host where WebPass Oracle HTTP Server instance is running and port refers to the HTTP port of the Oracle HTTP Server instance.

2. When prompted for a username and password, log in as an administrator. Click OK.

3. On the Access System main page, click the Access System Console link.

4. On the Access System Console page, click the Access System Configuration tab.

5. On the Access System Configuration page, click Host Identifiers at the bottom left.

6. On the List all host identifiers page, click on the host identifier created by the OAM Configuration Tool. For example, select SOA_EDG.

7. On the Host Identifier Details page, click Modify.

8. On the Modifying host identifier page, add all the possible host name variations for the host. Click the plus and minus symbols to add or delete fields as necessary. The Preferred HTTP Host value used in the Access System Configuration must be added as one of the host name variations. For example: soedg_wd, webhost1.mycompany.com:7777, admin.mycompany.com:7777.

9. Select the check box next to Update Cache and then click Save.

   A message box with the following message is displayed: "Updating the cache at this point will flush all the caches in the system. Are you sure?".

   Click OK to finish saving the configuration changes.

10. Verify the changes on the Host Identifier Details page.

11.2.3.5 Updating the WebGate Profile

The OAM Configuration Tool populates the Preferred_HTTP_Host and hostname attributes for the WebGate profile that is created with the value of the app_domain parameter. Both these attributes must be updated with the proper values for the configuration to work correctly. Follow the steps below to update the WebGate profile created by the OAM CFG Tool.

1. Navigate to the Access System Console by specifying the following URL in your web browser:

   http://hostname:port/access/oblix
   

   where hostname refers to the host where WebPass Oracle HTTP Server instance is running and port refers to the HTTP port of the Oracle HTTP Server instance.

2. On the Access System main page, click the Access System Console link, then log in as an administrator.

3. On the Access System Console main page, click Access System Configuration, and then click the Access Gate Configuration link on the left pane to display the AccessGates Search page.

4. Enter the proper search criteria and click Go to display a list of AccessGates.

5. Select the AccessGate created by the OAM Configuration Tool. For example: SOA_EDG_AG.

6. On the AccessGate Details page, select Modify to display the Modify AccessGate page.

7. On the Modify AccessGate page, update:

   • Hostname: Update the hostname with the name of the computer where WebGate is running, for example: webhost1.mycompany.com.

   • Preferred HTTP Host: Update the Preferred_HTTP_Host with one of the hostname variations specified in the previous section, for example: admin.mycompany.com:7777.

   • Primary HTTP Cookie Domain: Update the Primary HTTP Cookie Domain with the Domain suffix of the host identifier, for example: mycompany.com

8. Click Save. A message box with the "Are you sure you want to commit these changes?" message is displayed.

9. Click OK to finish updating the configuration.

10. Verify the values displayed on the Details for AccessGate page to confirm that the updates were successful.

11.2.3.6 Adding Additional Access Servers

To assign an Access Server to the WebGate:

1. Log in as the Administrator on the Access System Console.

2. Navigate to the Details for AccessGate page, if necessary. From the Access System Console, select Access System Configuration, then AccessGate Configuration, then the link for the WebGate (SOA_EDG_AG).

3. On the Details for AccessGate page, click List Access Servers.

4. A page appears showing the primary or secondary Access Servers currently configured for this WebGate.

   Click Add.

5. On the Add a New Access Server page, select an Access Server from the Select Server list, specify Primary Server, and define two connections for the WebGate.

   Click the Add button to complete the association.

6. A page appears, showing the association of the Access Server with the WebGate. Click the link to display a summary and print this page for later use.

7. Repeat steps 3 through 6 to associate more Access Servers to the WebGate.

11.2.3.7 Configuring Delegated Form Authentication

To configure the form authentication to redirect to the WebGate that was installed with the OAM installation, complete these steps:

1. Open the Access System Console.

2. In the Access System Configuration screen, select Authentication Management from the left-hand bar.

3. Select OraDefaultFormAuthNScheme.

4. Click Modify.

5. In the Challenge Redirect field, enter the host and port of the IDM installation; for example: http://sso.mycompany.com.

A WebGate should already be installed in the IDM installation. Refer to Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management for details.

11.2.4 Installing and Configuring WebGate

WebGate needs to be installed on each of the WEBHOSTn machines in order to secure the web tier:

1. Launch the WebGate installer (see Section 1.5.5, "What to Install" for information on where to obtain it) using the following command:

   ./Oracle_Access_Manager10_1_4_3_0_linux_OHS11g_WebGate –gui
   

2. The Welcome screen is displayed. Click Next.

3. In the Customer Information screen (Figure 11-1), enter the user name and user group that the web server is running as. Click Next to continue.

   Figure 11-1 Customer Information Screen

   
   Description of "Figure 11-1 Customer Information Screen"
   
   

4. In the installation target screen (Figure 11-2), specify the directory where WebGate should be installed. Click Next to continue.

   Figure 11-2 Installation Target Screen

   
   Description of "Figure 11-2 Installation Target Screen"
   
   

5. In the installation summary screen, click Next.

6. Download the required GCC runtime libraries for WebGate as instructed in the WebGate configuration screen (Figure 11-3), and use Browse to point to their location on the local computer. Click Next to continue.

   Figure 11-3 Runtime Libraries Screen

   
   Description of "Figure 11-3 Runtime Libraries Screen"
   
   

7. The installer now creates the required artifacts. After that is completed, click Next to continue.

8. In the transport security mode screen (Figure 11-4), select "Open Mode: No Encryption" and click Next to continue.

   Figure 11-4 Transport Security Mode Screen

   
   Description of "Figure 11-4 Transport Security Mode Screen"
   
   

9. In the WebGate configuration screen, provide the details of the Access Server that will be used. You must provide the following information:

   • WebGate ID, as provided when the OAM configuration tool was executed

   • Password for WebGate

   • Access Server ID, as reported by the OAM Access Server configuration

   • Access Server host name, as reported by the OAM Access Server configuration

   • Access Server port number, as reported by the OAM Access Server configuration

   Note:

   The Access Server ID, host name, and port are all required.

   You can obtain these details from your Oracle Access Manager administrator. Click Next to continue.

   Figure 11-5 Access Server Configuration Screen

   
   Description of "Figure 11-5 Access Server Configuration Screen"
   
   

10. In the Configure Web Server screen, click Yes to automatically update the web server. Click Next to continue.

11. In the next Configure Web Server screen, specify the full path of the directory containing the httpd.conf file. This file is located in the following directory:

    ORACLE_BASE/admin/<OHS_Instance>/config/OHS/<OHS_ComponentName>
    

    For example:

    /u01/app/oracle/admin/ohs_instance2/config/OHS/ohs2/httpd.conf
    

    Click Next to continue.

12. In the next Configure Web Server page, a message informs you that the Web server configuration has been modified for WebGate. Click Yes to confirm.

13. Stop and start your Web server for the configuration updates to take effect. Click Next to continue.

14. In the next Configure Web Server screen, the following message is displayed: "If the web server is set up in SSL mode, then the httpd.conf file needs to be configured with the SSL related parameters. To manually tune your SSL configuration, please follow the instructions that come up". Click Next to continue.

15. In the next Configure Web Server screen, a message with the location of the document that has information on the rest of the product setup and Web server configuration is displayed. Choose No and click Next to continue.

16. The final Configure Web Server screen appears with a message to manually launch a browser and open the HTML document for further information on configuring your Web server. Click Next to continue.

17. The Oracle COREid Readme screen appears. Review the information on the screen and click Next to continue.

18. A message appears (along with the details of the installation) informing you that the installation was successful.

11.2.5 Changing the CacheControl Headers in the SOA_EDG_AG for Oracle BAM

Some Oracle BAM objects are required to be present in the browser´s cache or temp folder in order to be executed. When Oracle Access Manager is used as the Single Sign-On system for Oracle BAM, the HTTP cache header for Web pages is, by default, set to "no-cache" for security reasons. This prevents Internet Explorer from properly accessing some objects, as described in this Microsoft Knowledge Base note http://support.microsoft.com/kb/316431, and can cause exceptions while clicking different menu items in Oracle BAM's console. You must change the CacheControl headers settings in the SOA_EDG_AG Access Gate to prevent these errors. To change these settings:

1. Navigate to the Access System Console using the following URL:

   http://hostname:port/access/oblix

   Where hostname refers to the host where the WebPass Oracle HTTP Server instance is running, and port refers to the HTTP port of the Oracle HTTP Server instance.

2. On the Access System main page, click the Access System Console link, then log in as an administrator.

3. On the Access System Console main page, click Access System Configuration, and then click the Access Gate Configuration link on the left pane to display the AccessGates Search page.

4. Enter the proper search criteria and click Go to display a list of AccessGates.

5. Select the AccessGate created by the Oracle Access Manager configuration tool.

6. Click Modify at the bottom of the page.

7. In the CachePragmaHeader and CacheControlHeader fields, replace the no-cache field with private.

8. Click Save at the bottom of the page.

11.2.6 Configuring IP Validation for the Webgate

IP Validation determines if a client's IP address is the same as the IP address stored in the ObSSOCookie generated for single sign-on. IP Validation can cause issues in systems using load balancer devices configured to perform IP termination, or when the authenticating webgate is front-ended by a different load balancer from the one front-ending the enterprise deployment. To configure your load balancer so that it is not validated in these cases, follow these steps:

1. Navigate to the Access System Console using the following URL:

   http://hostname:port/access/oblix

   Where the hostname refers to the host where the WebPass Oracle HTTP Server instance is running, and port refers to the HTTP port of the Oracle HTTP Server instance.

2. On the Access System main page, click the Access System Console link, and then log in as an administrator.

3. On the Access System Console main page, click Access System Configuration, and then click the Access Gate Configuration link on the left pane to display the AccessGates Search page.

4. Enter the proper search criteria and click Go to display a list of AccessGates.

5. Select the AccessGate created by the Oracle Access Manager configuration tool.

6. Click Modify at the bottom of the page.

7. In the IPValidationException filed, enter the address of the load balancer used to front-end the deployment.

8. Click Save at the bottom of the page.

11.2.7 Setting Up WebLogic Authenticators

This section assumes that you have already set up the LDAP authenticator by following the steps in Section 11.1.2.1, "Creating the LDAP Authenticator." If you have not already created the LDAP authenticator, do it before continuing with this section.

This section includes the following topics:

• Section 11.2.7.1, "Back Up Configuration Files"

• Section 11.2.7.2, "Setting Up the OAM ID Asserter"

• Section 11.2.7.3, "Setting the Order of Providers"

11.2.7.1 Back Up Configuration Files

To be safe, first back up the relevant configuration files:

ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/config.xml
ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/fmwconfig/jps-config.xml
ORACLE_BASE/admin/<domain_name>/aserver/<domain_name>/config/fmwconfig/system-jazn-data.xml

Also back up the boot.properties file for the Administration Server.

11.2.7.2 Setting Up the OAM ID Asserter

To set up the OAM ID Asserter, complete these steps:

1. Log into Weblogic Console, if not already logged in.

2. Navigate to SecurityRealms\<Default Realm Name>\Providers.

3. Click New and Select "OAM Identity Asserter" from the dropdown menu.

4. Name the asserter (for example, "OAM ID Asserter") and click Save.

5. Click the newly added asserter to see the configuration screen for OAM Identity Asserter.

6. Set the control flag to 'REQUIRED' and click Save.

7. Open the Provider Specific tab to configure the following required settings:

   • Primary Access Server: provide OAM server endpoint information in HOST:PORT format.

   • AccessGate Name: name of the AccessGate (for example, SOA_EDG_AG).

   • AccessGate Password: password for the AccessGate (optional).

8. Save the settings.

11.2.7.3 Setting the Order of Providers

Reorder the OAM Identity Asserter, OID Authenticator, and Default Authenticator by ensuring that the control flag for each authenticator is set as follows:

• OAM Identity Asserter: REQUIRED

• OID LDAP Authenticator (or OVD LDAP Authenticator): SUFFICIENT

• Default Authenticator: SUFFICIENT

11.3 Backing Up the Installation

After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At this point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrator's Guide provides further details. For information on describing the Oracle HTTP Server data that must be backed up and restored, refer to the "Backup and Recovery Recommendations for Oracle HTTP Server" section in this guide. For information on how to recover components, see "Recovery of Components" and "Recovery After Loss of Component" sections in the guide. For recommendations specific to recovering from the loss of a host, see the "Recovering Oracle HTTP Server to a Different Host" in the guide. Also refer to the Oracle Database Backup and Recovery User's Guide for information on database backup.

To back up the installation a this point, complete these steps:

1. Back up the web tier:

   1. Shut down the instance using opmnctl.

      ORACLE_BASE/admin/<instance_name>/bin/opmnctl stopall
      

   2. Back up the Middleware Home on the web tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web.tar $MW_HOME
      

   3. Back up the Instance Home on the web tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web_instance.tar $ORACLE_INSTANCE
      

   4. Start the instance using opmnctl:

      ORACLE_BASE/admin/<instance_name>/bin/opmnctl startall
      

2. Back up the AdminServer domain directory. Perform a backup to save your domain configuration. The configuration files all exist under the ORACLE_BASE/ admin/<domain_name> directory.

   SOAHOST1> tar -cvpf edgdomainback.tar ORACLE_BASE/admin/<domain_name>