Configure the Maximum Lifetime for New Emergency Access Tokencodes
Last Modified: 2026-08-25
Configure the Maximum Lifetime for New Emergency Access Tokencodes
You can use the auth_manager.admin.eatokencode_expire_days global configuration value to set the maximum number of days that new Emergency Access Tokencodes can remain active. When a user or administrator activates a new Emergency Access Tokencode, they will not be allowed to set the expiration date later than the maximum lifetime you specify.
Procedure
Run the following command and then restart Authentication Manager services:
./rsautil store -a add_config auth_manager.admin.eatokencode_expire_days days_value GLOBAL 501
where days_value is the maximum number of days that new Emergency Access Tokencodes can remain active.
Related Articles
What maximum number of characters allowed in form control type "Text Area" for use in RSA Identity Governance and Lifecycle 21Number of Views Configure Emergency Access for Provisioning 31Number of Views SID: When importing a software token on a Mac getting password prompt. 8Number of Views Cloud Access Service - Authentication Methods and Emergency Access 8Number of Views RADIUS Server configuration warning in RSA Authentication Manager 8.1 SP1 244Number 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?