In this Document
Symptoms |
Cause |
Solution |
APPLIES TO:
Oracle Access Manager - Version 11.1.2.3.170418 and laterInformation in this document applies to any platform.
SYMPTOMS
- Oracle Access Manager (OAM) 11.1.2.3 Idle Timeout not Working, Regardless of User Activity, Within the 15 Minutes the Users are Redirected for Authentication
- No Multi Data Center (MDC) architecture
- Using Embedded Credential Collector (ECC)
- Does not have any Application Domain timeouts set
CAUSE
SSOONLYMode parameter in oam-config.xml file is set to "true"
When SSOOnlyMode is set to TRUE , authorization is skipped by OAM so the last access time is never updated.
When SSOOnlyMode is set to TRUE , authorization is skipped by OAM so the last access time is never updated.
SOLUTION
1. Change
<Setting Name="SSOOnlyMode" Type="xsd:boolean">true</Setting>
to
<Setting Name="SSOOnlyMode" Type="xsd:boolean">false</Setting>
2. Increase the version value in the oam-config.xml file to one numerical value higher
For Ex.
<Setting Name="FilePollingInterval" Type="xsd:integer">30000</Setting>
<Setting Name="NotificationLockWait" Type="xsd:integer">20000</Setting>
<Setting Name="Version" Type="xsd:integer">346</Setting>
o
<Setting Name="FilePollingInterval" Type="xsd:integer">30000</Setting>
<Setting Name="NotificationLockWait" Type="xsd:integer">20000</Setting>
<Setting Name="Version" Type="xsd:integer">347</Setting> -------------------> you only need to change this Version parameter value
<Setting Name="NotificationLockWait" Type="xsd:integer">20000</Setting>
<Setting Name="Version" Type="xsd:integer">346</Setting>
o
<Setting Name="FilePollingInterval" Type="xsd:integer">30000</Setting>
<Setting Name="NotificationLockWait" Type="xsd:integer">20000</Setting>
<Setting Name="Version" Type="xsd:integer">347</Setting> -------------------> you only need to change this Version parameter value
3. Start OAM Admin Server followed by Managed Servers
No comments:
Post a Comment