Oracle Products Integrated with Oracle Access Manager 11g (OAM) Known Logout Issues
(Doc ID 2199935.1)
Last updated on SEPTEMBER 05, 2023
Applies to:
Oracle Access Manager - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Goal
When dealing with logout issue with Oracle products integrated with Oracle access Manager 11g, the fist thing to verify is that the Oracle Access Manager 11g (OAM) logout basics are happening.
Call the OAM logout directly and should see a flow similar to the following:
1.http://<OAM_HOSTNAME>:<OAM_PORT>/oam/server/logout
This Terminate the session in the session store and Invalidates the OAM_ID cookie
2. This calls http://<OHS_WEBGATE_HOST>:<OHS_WEBGATE_PORT>/oam_logout_success
This deletes any of the OAMAuthnCookies which individual WebGates
3. Than calls http://<OAM_HOSTNAME>:<OAM_PORT>/oam/pages/logout.jsp
Physical page displayed
- This can be confirmed in an http header trace.
- A successful logout has occurred when invoking /oam/server/logout. Both OAM_ID and OAMAuthnCookie are expired. If there are issue with the other applications specific cookies not being cleared, they will need to be addressed by that specific team. Below are KM notes for known issue.
Solution
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
Goal |
Solution |
References |