Require Users to Change Their RSA SecurID PINs
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 29Number of Views How to change RSA SecurID token policies to require 6-character or 8 character PINs 213Number of Views Changes to JSP files require an application restart to take effect in RSA Identity Governance & Lifecycle 67Number of Views Changes to Forms in Workflow Approval and Activity Nodes require an application restart to take effect in RSA Identity Gov… 55Number of Views Require a User to Change a Password using the User Dashboard 105Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Release Notes (January 2026) AFX Server Fails to Start with 'Could Not Build a Validated Path' and 'Timed Out Waiting for AFX Applications to Start' in…
Don't see what you're looking for?