Types of Session Lifetime Limits
Session settings apply to the logon pages for the web-based administrative consoles, the command API interface described in the RSA Authentication Manager Developer’s Guide, and the risk-based authentication (RBA) logon attempts by end users. When a session times out or reaches the maximum lifetime, the logon page is redisplayed, and the user must log on again.
You can configure the following settings for sessions:
Time-out. The length of time that a session can be inactive before being terminated. The default setting is 30 minutes.
Maximum Lifetime. The maximum length of an session. When the console session reaches its session lifetime, the session is terminated and the administrator is logged off, regardless of whether the session is active. The default setting is eight hours.
These settings are independent of session inactivity. For example, if a console and command API session lifetime is eight hours, an administrator is automatically logged off after eight hours, even if there have been no periods of inactivity during the session.
Only a Super Admin can modify the console and command API session settings.
Related Tasks
Related Articles
Install the Identity Router Virtual Appliance for VMware 98Number of Views RSA Authentication Manager 8.8 VMware Virtual Appliance Getting Started 84Number of Views RSA Authentication Manager 8.9 VMware Virtual Appliance Getting Started 18Number of Views How to install one RSA SecurID software token on multiple devices 615Number of Views Add, Delete, and Test the Connection for an Identity Source in Cloud Access Service 508Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…