OAM coexistence usecase : 10g to 11g does not work after upgrading OAM to OAM (BP 12)

(Doc ID 2340025.1)

Last updated on JANUARY 22, 2018

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


Problem Description
OAM coexistence does not work after upgrading from OAM to OAM (BP 12)

Behavior seen

1. OAM 11g login works fine
2. OAM 11g login followed by accessing a 10g resource works fine
3. OAM 10g login followed by accessing an 11g resource FAILS


1. Enable co-existence after copying "US_export_policy.jar” and “local_policy.jar to Java security directory.

2. Commands ran to enable co-existence:
a. setCoexistenceConfigWith10G(ldapUrl="ldap://qa-uisldap.mhf.mhc:3890", ldapPrinciple="uid=sys-oam_admin,ou=people,ou=intranet,dc=mhc", ldapConfigBase="ou=oam1043,ou=applications,ou=intranet,dc=mhc", coexCookieDomain=".mhf.mhc")
b. enableOamAgentCoexistWith10G()

3.Access 10g to 11g application, SSO failed to work

4. Access 11g to 10g application, SSO is successful


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms