Last updated on SEPTEMBER 28, 2016
Applies to:Oracle Access Manager - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 11g to 12c]
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms