My Oracle Support Banner

OAM 11g: Single Sign-On Not Working Between OAM Agent And OSSO Agent (Doc ID 1439710.1)

Last updated on OCTOBER 20, 2020

Applies to:

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


In OAM 11g BP01 Protected a resource using 10g webgate and another resource using OSSO Agent which are in same cookie domain.

Both the Authentication schemes are on the same level.
Single Sign On do not works when user access webgate resource first.
User is asked to re-authenticate when he access resource protected by OSSO agent after accessing webgate resource first.
However Single Sign On works perfectly fine when he access webgate resource after accessing OSSO resource first.
Note: This is noticed on a environment where 10g SSO was migrated to
oam-diagnostic.log shows the below message:
 [SRC_CLASS: AMCoexistSessionSynchHandler] [APP: oam_server] [SRC_METHOD: syncSSOCoexistSession] [URI: /oam/server/osso_login] Retrieve SSO session operation failed.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.