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
Changes to JSP files require an application restart to take effect in RSA Identity Governance & Lifecycle 68Number of Views Report filter does not take changes in RSA Identity Governance and Lifecycle 15Number of Views Require a System-Generated PIN 30Number of Views RSA Governance & Lifecycle - Onboarding Framework v3 9Number of Views How to verify that changes made to cknfastrc file have taken affect for supporting SSL keys based on nCipher/Thales PKCS#1… 69Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?