Oracle Access Manager 11g R2PS2 (OAM 11.1.2.2) - Settings for User's Session Restrictions Does not Work for Value 100
(Doc ID 2168431.1)
Last updated on OCTOBER 31, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.2.1 and laterInformation 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
Setting the Maximum Number of Sessions per User to 100 does not work
Configured OAM Global Session Lifecycle Settings as following:
Session Lifetime: 900 (minutes)
Idle Timeout: 0 (minutes)
Maximum Number of Sessions per User: 100
Database Persistence of Active Sessions Enabled: Checked
Idle Timeout: 0 (minutes)
Maximum Number of Sessions per User: 100
Database Persistence of Active Sessions Enabled: Checked
Observed that a user has more than 100 sessions. So this restriction does not work.
...
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 |