Last updated on JULY 06, 2017
Applies to:Oracle Access Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
1. DCC Login is being used with Co-existence enabled, so ObSSOCookie is source of truth.
2. Accessed Apache resource first, logged in using DCC and then in a new tab accessed IIS resource. SSO working as expected.
3. Logged out using DCC logout (:8080/oamsso-bin/logout.pl), callbacks were sent to both resource Webgates, as expected. However, we got a 504 error for IIS callback request, so IIS Webgate did not clean-up its OAMAuthnCookie.
4. Repeated the testcase with IIS resource access first, same behavior is observed.
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