New PINs and On-Demand Tokencodes for Authentication Agents and RADIUS Clients
On-demand tokencodes always require a PIN. As a result, an administrator cannot clear the PIN of a user with an on-demand tokencode without assigning a temporary PIN. The user experience of changing the PIN of an on-demand tokencode depends on the method used to request the tokencode.
For a tokencode requested through an authentication agent or RADIUS client:
The user attempts to access a protected resource, and the agent prompts the user to enter a User ID and passcode.
When prompted for the passcode, the user enters the current PIN, which could be an expiring PIN or a temporary PIN assigned by the administrator.
The agent prompts the user to enter a new PIN and to confirm the new PIN.
The user enters a new PIN and confirms the new PIN.
The agent prompts the user to enter a passcode.
The user enters the new PIN.
AM sends the on-demand tokencode to the user.
When the agent prompts the user for next tokencode, the user enters the received on-demand tokencode.
Related Articles
"Error editing the Location update T_AV_CRSUBMISSION_FIELDS" when defining new Form Fields in RSA Identity Governance & Li… Number of Views SecurID: How to verify if TCP/UDP ports are allowed between a Linux machine and Authentication Manager. Number of Views Cloud Administration Console Dashboard Number of Views How to import CA signed console cert from AM 8.x primary into a new primary with same FQDN Number of Views Workflow variable ${jobUserData_WorkItemURL} doesn't get resolved for email reminder workflow in RSA Identity Governance a… Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager Upgrade Process
