Configure the Maximum Lifetime for New Emergency Access Tokencodes
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
Configure Emergency Access for Provisioning 30Number of Views RSA MFA Agent 2.5 for Microsoft Windows Third-Party Licenses 6Number of Views Custom Account Attribute mapped to the Active Directory accountExpires attribute no longer collects a value after upgradin… 97Number of Views RSA Announces the Release of RSA MFA Agent 2.4.3 for Microsoft Windows 104Number of Views RSA MFA Agent 2.4.3 for Microsoft Windows Release Notes 91Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide User Event Monitor Messages for Cloud Access Service (1501 - 20406) RSA Release Notes for RSA Authentication Manager 8.8 Troubleshooting RSA MFA Agent for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Group Policy Object Template Guide
Don't see what you're looking for?