Using OAM 22.214.171.124.210920, When the Session Timeout, the Relogin Fails and Results in Looping and Keeps Spinning
(Doc ID 2876144.1)
Last updated on JUNE 13, 2022
Oracle Access Manager - Version 126.96.36.199.210920 and later Information in this document applies to any platform.
Using OAM 188.8.131.52.210920.
OAM is configured as SP.
Once the idle time is exceeded, the session timeout and user refreshes browser to try and relogin, this results in looping and keeps spinning and never comes back.
If the user opens two applications in two tabs and logout from one of the tab and try to access the application from the other tab that did not logout, user will be redirected back to the log in page successfully.
Relogin works fine if the session is killed by logout but relogin fails when the session timeout.
There is a workaround by starting over in a new browser and relogin.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!