Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11g to 12c]
Information in this document applies to any platform.
Our facility has two OAM stacks running - one is run by the parent institution and one is run by our group. By default, logging in to an app protected by our OAM, sets the OAMAuthnHintCookie to '1'. However, the institution OAM requires it to be set to '0' in order to visit unprotected pages. Users that log in to our group's apps and then visit the institution pages, get an error and are unable to view institution pages. Is there a way to rename the cookie? Should we change our OAMAuthnHintCookie to '0'. If so how is that done? Do you have any suggestions on how to handle this (other than the workaround that a user can clear cookies or use a different browser)?
- Protected resources work separately
- Deleting the OAMAUTHNHINTCOOKIE between calls to OAM A resources and OAM B resources, resolves the issue, but is not practical.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms