My Oracle Support Banner

Exceeding Sessions Can Be Generated after Idle Time Is Reached (Doc ID 2044994.1)

Last updated on OCTOBER 24, 2023

Applies to:

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


Exceeding sessions after the "Idle Timeout(minutes)" is reached.

Step by step for reproduction.

1.In Common Settings on Oracle Access Manager (OAM) Console, the following is set at each setting.

  Session Lifetime (minutes)=480(default value)
  Idle Timeout (minutes)=2
  Maximum Number of Sessions per User=2

2.Invoke a browser and access a resource.

3.Log in via OAM authentication as "UserA".
  This is first session.

4.In another machine invoke a browser and access the resource.

5.Log in via OAM authentication as "UserA".
  This is a second session and it indicates the session limit is reached.

6.In other machine, try accessing and logging into the resource as "userA".
  You will encounter the following message on your browser.
  The user has already reached the maximum allowed number of sessions.
   Please close one of the existing sessions before trying to login again.

  "Maximum Number of Sessions per User" works fine.

7.After two minutes, try accessing and logging in to the resource again from the machine of the step3 as "UserA".
  It will be successful to access the resource.

8.Refresh the browsers of the first and second sessions, the browsers show the login page for re-authentication.
  After logging in, you will be able to access the resource on the first and second sessions.
  At that time you can see three sessions of "userA" from Session Management.




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

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