Set an Initial On-Demand Authentication PIN for a User
On-demand authentication (ODA) always requires a PIN to request a tokencode. You can set the initial PIN for the user. The following procedure is for a user who is not yet enabled for ODA.
Procedure
In the Security Console, click Identity > Users > Manage Existing.
Use the search fields to find the user for whom you want to enable ODA and set an initial PIN.
Click the user.
Select SecurID Tokens.
Under On-Demand Authentication, select Enable User.
For Expiration Date, specify No expiration or the date when on-demand authentication expires.
For Send On-Demand Tokencodes to, specify the delivery method.
For Associated PIN, do one of the following:
Select Require user to setup the PIN through RSA Self-Service Console.
Select Set initial PIN to, and enter the initial PIN.
Click Save.
If you have set the initial PIN, securely communicate the initial PIN to the user.
Related Concepts
Related Articles
How to set a new PIN for RSA SecurID Tokens in RSA Authentication Manager 8.6 or later using NTRadPing Utility 135Number of Views How to reset table views to their original factory-set (OOTB) defaults in RSA Identity Governance & Lifecycle 33Number of Views Generating a Software Token Report with extra information for Authentication Manager 8Number of Views How to manually set the date and time on an RSA Identity Governance & Lifecycle hardware appliance 306Number of Views The approval workflow isn't working as expected when grouping by business source in the request form with the provisioning… 29Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory