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
VM malformed request seen in logs 15Number of Views Configure Initial Network Settings Using the Identity Router VM Console 130Number of Views Error "Warning NTP and VM Host TimeSync should not be enabled at the same time" in RSA Authentication Manager 89Number of Views RSA MFA Agent 9.0 for PAM - Installation and Configuration Guide for Solaris 71Number of Views Configure Network Settings Using the Identity Router Setup Console 111Number 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