Require Users to Change Their RSA SecurID PINs
Last Modified: 2026-08-25
Require Users to Change Their RSA SecurID PINs
When you require a user to change a SecurID PIN, the user is prompted to create a new PIN after successfully authenticating with the token.
You can require a PIN change only when a user knows the existing PIN. For example, you might require a user to change a SecurID PIN if the current PIN has been compromised. If a user has forgotten the PIN, clear the PIN.
Procedure
In the Security Console, click Authentication > SecurID Tokens > Manage Existing.
Click the Assigned tab.
Use the search fields to find the token that you want to edit.
From the search results, click the token with the PIN that you want the user to change.
Select Require SecurID PIN Change.
Related Articles
Require a System-Generated PIN 30Number of Views Changes to JSP files require an application restart to take effect in RSA Identity Governance & Lifecycle 68Number of Views Use the User Dashboard to Require PIN Changes 11Number of Views Report filter does not take changes in RSA Identity Governance and Lifecycle 15Number of Views RSA Identity Governance and Lifecycle Workflow Activity Node of type Decision Node based on internal variables always eval… 106Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process Quick Setup Guide - Connect Authentication Manager to Cloud Authentication Service IDR SSO - Step 3: Deploy the Identity Router Unexpected error during command com.rsa.ucm.request.CompleteWorkflowRequestActionsCommand execution when approving token r…
Don't see what you're looking for?