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 RSA Governance & Lifecycle - Onboarding Framework v3 9Number of Views Require a System-Generated PIN 30Number of Views RSA Via Lifecycle and Governance 7.0 Global Roles do not show under matching entitlements when entitlement rule is set to … 21Number of Views How to change RSA SecurID token policies to require 6-character or 8 character PINs 213Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle
Don't see what you're looking for?