My Oracle Support Banner

Oracle Access Manager (OAM) Federated Authentication Looping After Logging Out of a Different OAM Environment (Doc ID 3009125.1)

Last updated on MARCH 14, 2024

Applies to:

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


When attempting to access an OAM environment using federated authentication where OAM is the Service Provider (SP) after logging out of a separate environment using federated authentication, the browser repeatedly authenticates with the federated Identity Provider and eventually reports that the user has reached the maximum number of OAM sessions in the browser.  Note that a similar behavior could potentially occur in a non-federated environment but in that case it would likely result in looping between the webgate protected URL and the OAM managed server's obrareq.cgi endpoint (without reaching maximum sessions).


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.