Communications Express with Access Manager SSO, Session Timeout Happens Too Soon
(Doc ID 1314410.1)
Last updated on JANUARY 26, 2024
Applies to:
Communications Express for Oracle Communications - Version 6.1 to 6.3 [Release 6.1 to 6.3]Information in this document applies to any platform.
Symptoms
Environment:
- Communications Express / Unified Web Client (UWC) 6.3, 122794-21.
- Sun Java Enterprise System Access Manager 7.1.
- Communications Express is configured to use Access Manager single sign-on (SSO).
- Messaging Server 7.0.
The Access Manager session timeout* was set to 120 minutes (2 hours), and idle timeout was set to 30 minutes.
However, users were getting session timeout sooner than 2 hours, even while actively using Communications Express.
*How to check the Access Manager session timeout:
Using a browser, go to the Access Manager Console (http://hostname/amconsole), login as amAdmin.
Select:
Configuration tab -> Global Properties -> Session -> Dynamic Attributes
the settings are "Maximum Session Time" and "Maximum Idle Time".
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 |
| References |