OAM22.214.171.124.x - Application Domain Idle time out is behaving as session time out
(Doc ID 2148951.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Access Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The Application domain Session Idle time out is working as session time out but not as Idle time out.
Global Session/Idle timeout settings
Max Session Lift Timeout== 30Mins
Idle session time out==15Mins
Settings at Application domain Level
Application domain Idle session timeout =4 Mins
Case 1: Success
Lets say user access an application at 3.30 PM and the Idle session time out set to 3.34 PM. If the user is idle for 4 Mins, The OAM is forcing user to go
Case 2: Failure
User logged in at 3.30 PM and access the application at 3.32 PM. So the new Idle session time out should set to 3.36 PM. But after 3.34 PM, OAM is
forcing user to go through authentication. So basically the max session time is getting kicked in, even in Success (Above) case
The same configuration working properly in OAM 188.8.131.52
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