51.3 Deploying Mobile and Social With Oracle Access Manager

Mobile and Social can be configured for use with either Oracle Access Manager 10g or 11gR1 PS1.

For this to work, however, Oracle Access Manager and Mobile and Social need to be installed on different servers in different domains. Mobile and Social and Oracle Access Manager then need to be configured to work together. The following procedure documents how to do this using Oracle Access Manager 11gR1 PS1. Before you Begin - Install Social Identity on Host 1 and Oracle Access Manager 11gR1 PS1 on Host 2.

To deploy mobile and social with Oracle Access Manager:

1. Log on to the Oracle Access Management Console on Host 2 and create a Webgate profile for Social Identity using the default settings.

2. In Social Identity, create an Authentication Service Provider for Oracle Access Manager 11.1.1.5.

   See Creating an Authentication Service Provider.

   Set the Attributes as described in the following table.

   Table 51-1 Attribute Settings for an Oracle Access Manager 11gR1 PS1 Authentication Service Provider

   Name	Value
   OAM_VERSION	OAM_10G
   DEBUG_VALUE	0
   TRANSPORT_SECURITY	OPEN
   OAM_SERVER_1	host:port
   OAM_SERVER_1_MAX_CONN	4
   OAM_SERVER_2	host:port
   OAM_SERVER_2_MAX_CONN	4
   AuthNURL	wl_authen://Authen/Basic

3. In Social Identity, create a Service Profile for the Authentication Service Provider that you created in the previous step.

   See Defining Service Profiles.

4. In Social Identity, create a Service Domain.

   See Creating a Service Domain.

5. Merge the cwallet.sso file on Host 2 with the cwallet.sso file on Host 1 as follows:

   1. Copy cwallet.sso from Host 2 to Host 1.

   2. On Host 1 type

      # mkdir /tmp/oam  /tmp/oic# cp <host>/cwallet.sso /tmp/oam    # cp config/fmwconfig/cwallet.sso /tmp/oic  
          
      

   3. Create file merge-creds.xml:

      <?xml version="1.0" encoding="UTF-8" standalone='yes'?>
      <jpsConfig xmlns="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd"
      schema-major-version="11" schema-minor-version="1">
        <serviceProviders>
          <serviceProvider
      class="oracle.security.jps.internal.credstore.ssp.SspCredentialStoreProvider"
      name="credstoressp" type="CREDENTIAL_STORE">
            <description>File-based credential provider</description>
          </serviceProvider>
        </serviceProviders>
        <serviceInstances>
          <!-- Source file-based credential store instance -->
          <serviceInstance location="/tmp/oam" provider="credstoressp"
      name="credential.file.source">
          </serviceInstance>
          <!-- Destination file-based credential store instance -->
          <serviceInstance location="/tmp/oic" provider="credstoressp"
      name="credential.file.destination">
          </serviceInstance>
        </serviceInstances>
        <jpsContexts>
          <jpsContext name="FileSourceContext">
            <serviceInstanceRef ref="credential.file.source"/>
          </jpsContext>
          <jpsContext name="FileDestinationContext">
            <serviceInstanceRef ref="credential.file.destination"/>
          </jpsContext>
        </jpsContexts>
      </jpsConfig>
      

   4. Set the path variable to include $MW_HOME/oracle_common/bin:$MW_HOME/oracle_common/common/bin

   5. Execute the command to merge the cwallet.sso files:

      # wlst.shwlst:/> migrateSecurityStore(type="credStore", configFile="/tmp/mergecreds.xml",src="FileSourceContext",dst="FileDestinationContext")
      

   6. Copy the merged file to config/fmwconfig:

      # cp /tmp/oic/cwallet.sso /scratch/kerwin/wls10/user_projects/domain/base_domain/cfnfig/fmwconfig
      

   7. Restart the OAM Server on Host 1.