Provide an Offline Emergency Access Tokencode
A user needs offline emergency access when the user's Windows device cannot contact the AM server through the network and the user's RSA SecurID Token is unavailable, or the user forgot his or her PIN.
You can provide an offline emergency access tokencode to replace the token generated by the user's RSA SecurID Token or RSA Authenticator app. RSA SecurID users must enter the offline emergency access tokencode with a PIN to perform two-factor authentication. Authenticate app users enter the offline emergency access tokencode without a PIN.
You can configure the following:
Specify that a new offline emergency access tokencode is downloaded the next time the user authenticates online.
Allow the offline emergency access tokencode to be used for online and offline authentication.
You can provide an offline emergency access tokencode on any primary or replica instance.
Before you begin
The user’s security domain must allow offline authentication and permit the user to download offline emergency access tokencodes.
The user must have authenticated to an agent that supports offline authentication and the agent has downloaded days of offline authentication data.
Procedure
In the Security Console, click Authentication > SecurID Tokens > Manage Existing.
Use the search fields to find the token for the user who needs an offline emergency access tokencode.
From the search results, click the token.
From the context menu, click Emergency Access Tokencodes.
On the Manage Emergency Access Tokencodes page, note the Offline Emergency Access Tokencode and its expiration date.
Select Reset Offline Emergency Access Tokencode, if you want the user to download a new offline emergency access tokencode the next time he or she authenticates online. If selected, the new tokencode downloads automatically.
Click Use offline code for online access, if you want the offline emergency access tokencode used for online authentication.
Click Save.
Related Articles
Provide an Offline Emergency Passcode 20Number of Views Require the Security Console and Self-Service Console to Provide the Same Response for Valid and Invalid Usernames 24Number of Views com.rsa.kms.key.support.KeyProviderException: Client failed to provide certificate 26Number of Views Why am I being asked to provide an On-Demand Authentication (ODA) PIN when logging in to the RSA Community? 55Number of Views Emergency Access for Cloud Access Service Users 110Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)