Last updated on MAY 02, 2017
Applies to:Oracle Access Manager - Version 184.108.40.206.0 to 220.127.116.11.5 [Release 11g]
Information in this document applies to any platform.
After upgrading from PS2 BP04 to PS3 BP05, sessions are cut of at exactly 8 hours after having logged in, despite the fact that Expiry time is set to 15 hrs.
This is happening only in HA environment, when both nodes are up.
Checking in the oam-config.xml "Expiry" is set to 15h:
<Setting Name="Expiry" Type="htf:timeInterval">900 M</Setting>
while in the database sessions get created with the expected duration (15hrs), then they get reset to the default value of 8 hrs:
SQL> select USERID, CRED_TIMEOUT_INTERVAL, TIMEOUT_INTERVAL, CREATE_TIME, EXPIRY_TIME, sessionid from fmw_oam.oam_session
user1 57600 18000 21/06/16 07:56:34,973000000 21/06/16 22:56:34,973000000 c36ab3cf-a46a-4b18-a9d8-808880b3182d|SuvLIdTaHgyOkiDC4Wv026p5PSo=
while using the session for a while, the expiry time has suddenly changed to 15:5x:xx instead of 22:5x.xx :
user1 57600 18000 21/06/16 07:56:34,973000000 21/06/16 15:56:34,973000000 c36ab3cf-a46a-4b18-a9d8-808880b3182d|SuvLIdTaHgyOkiDC4Wv026p5PSo=
Upgrade from PS2 to PS3.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms