Enabling Application Logout (Deep Logout) during Logout with Oracle Access Manager 11g (OAM)
(Doc ID 1969416.1)
Last updated on DECEMBER 08, 2022
Applies to:
Oracle Access Manager - Version 11.1.2.0.0 to 12.1.2.0.0 [Release 11g to 12c]Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Goal
This document describes how to execute application/deep logout as part of Oracle Access Manager 11g Logout, which is functionality that was present in OSSO 10g.
Some applications may require specific clean up to occur (such as removing unnecessary resources, terminating locally managed sessions, etc) when a user logs out of OAM 11g. If a user logs out of an application, it is up to that application to perform this clean up before forwarding the logout request to OAM/WebGate. However, if the user logs out of another OAM protected application, or invokes the OAM server logout directly, a callback to all OAM WebGates is necessary to ensure that applications protected by that WebGate have performed any necessary clean up.
This document specially discusses the mechanism provided by OAM 11g to facilitate application clean up on logout aka Deep Logout.
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 |
| Use Logout Callback URL of the 11g Application WebGate |
| Register logout callbacks with the OAM Sever |