My Oracle Support Banner

OAM Session is Deleted After 8 Minute Idle Timeout, Ignoring the Application Domain and Global Idle Timeout Settings (Doc ID 2683114.1)

Last updated on JUNE 25, 2020

Applies to:

Oracle Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

Customer is using a global idle timeout of 30 minutes and an application domain idle timeout setting of 20 minutes. However, OAM Sessions are getting deleted from the OAM Server after 8 minutes of being idle, well before either of the configured idle session timeout values.

Changes

 

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.