My Oracle Support Banner

Oracle Access Manager 11g R2PS2 (OAM 11.1.2.2) Idle Sessions Are Not Getting Terminated Even After Reaching The Configured Idle Session Timeout (Doc ID 1996702.1)

Last updated on NOVEMBER 05, 2019

Applies to:

Oracle Access Manager - Version 11.1.2.2.2 and later
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.

Symptoms

Configured the OAM sessions to have 'Maximum of Number of Session per User" to 1 and idle timeout (minutes) set to 30.
Per documentation: Maximum Number of Sessions per User
"Specifying the count as "1", activates a special mode. If a user who already has a session authenticates using another device (thereby creating a new session), then their existing session is deleted. No error is reported and no warning is given."
 
However, after a user logins and leaves the session inactive when come back an hour later and try to re-login the following OAM error screen appears:

"The user has already reached the maximum allowed number of sessions. Please close one of the existing sessions before trying to login again"

The expected behavior would be for OAM to terminate idle sessions after 30 minutes.

It worked correctly before OAM BP02 (11.1.2.2.2).

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


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