OAM SSO Re-Authentication Does Not Work After Some Inactivity Timeout
(Doc ID 2868386.1)
Last updated on MAY 14, 2023
Applies to:
Oracle WebLogic Server - Version 10.3.6 and laterInformation in this document applies to any platform.
Symptoms
Using OAM for SSO applications and encountering the following problem:
User A logs in app1 & app2 . Due to inactivity timeout, the user gets re-authenticated to app1 as user B. But App2 continues to show as logged user user A .
Cause
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
Symptoms |
Cause |
Solution |
References |