Require a System-Generated PIN
A user’s token policy determines whether his or her SecurID PIN must be system-generated. System-generated PINs are more secure because they are randomly selected by the server. This prevents a user from selecting a PIN that is easy to guess.
To require system-generated PINs, you must edit the token policy.
RSA RADIUS does not allow system-generated PINs by default. If the token policy requires system-generated PINS, you must edit the RADIUS configuration file securid.ini. For instructions on editing RADIUS configuration files, see Edit RADIUS Server Files.
Procedure
In the Security Console, click Authentication > Policies > Token Policies > Manage Existing.
Use the search fields to find the token policy that you want to edit.
From the search results, click the token policy that you want to edit.
From the context menu, click Edit.
Use the PIN Creation Method buttons to select Require system-generated PIN.
Click Save.
Related Articles
Require Users to Change Their RSA SecurID PINs Number of Views Changes to Forms in Workflow Approval and Activity Nodes require an application restart to take effect in RSA Identity Gov… Number of Views Guidelines for supporting Business Continuity and Availability Options in RSA Identity Governance & Lifecycle Number of Views How to change RSA SecurID token policies to require 6-character or 8 character PINs Number of Views How RSA Cloud Access Service Push Authentications Work (Approve and Device Biometrics) Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 Troubleshooting RSA MFA Agent for Microsoft Windows How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle The Template ({Connector Template Name}) has missing file content error when creating AFX Connectors in RSA Identity Gover…
