How to set a session timeout when accessing the Admin Console to automatically log out the user after a certain period of time?
Originally Published: 2008-02-05
Last Modified: 2023-10-06
Article Number
Applies To
Apache Tomcat 5.5.x
Issue
User is not logged out automatically based on a session timeout short enough.
Resolution
Currently we have the ability to set a session timeout. This is a configurable value in the application server setup. The user is forced to log back into the admin console after that period of inactivity is reached.
To adjust the value in an application server like Tomcat, locate the [Tomcat_home]/conf/web.xml file and change the following value:
<session-config>
<session-timeout>30</session-timeout>
</session-config>
Notes
Related Articles
Difference between a Delegate Reviewer and Alternate Manager in Access Certifications using Identity Governance & Lifecycle 39Number of Views User delete operations take an excessive period of time to perform on excessively large static groups in RSA Access Manage… 23Number of Views How to hide or disable the Set Out Of Office button in RSA Identity Governance & Lifecycle 48Number of Views RSA SecurID Authenticator 4.1 for iOS and Android Quick Start Guide (Italian) 8Number of Views Exclusion in workflow approval node not working if Out Of Office is set for an approver in RSA Identity Governance & Lifec… 58Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?