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 How to change RSA SecurID token policies to require 6-character or 8 character PINs 214Number of Views Require Password Change at Next Logon 20Number of Views Report filter does not take changes in RSA Identity Governance and Lifecycle 15Number of Views RSA Identity Governance & Lifecycle Access Fulfillment Express (AFX) Change Requests that depend on Entitlements Require A… 410Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?