Oracle Access Manager 11g (OAM 220.127.116.11) What is the Expected Behavior When a Different Username/Password is Used When the Idle Session Timeout Forces Login?
(Doc ID 2302651.1)
Last updated on AUGUST 24, 2020
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Oracle Access Manager 11gr2ps3 (OAM 22.214.171.124.x) What is the Expected Behavior When a Different Username/Password is Used When the Idle Session Timeout Forces Login
Steps to reproduce
- Protected application : myportal.com
- Idle session timeout = 15 min
- Max session timeout = 60 min
1. Access myportal.com and Login as userA
2. On the 16th minute refresh of myportal.com, now a login screen is displaid
3a. Login as userA and am able to access the portal
So far so good. OAM is working as expected.
3b. Instead of logging in as userA, login as userB ... The login keeps failing with OAM-2, then after 5 attempts OAM-10 error.
NOTE: Open another browser (say firefox, if the userA session was opened in chrome) can login as userB with same password.
The question is, why it does not allow login as userB on Idle session time out?
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