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 Require a User to Change a Password using the User Dashboard Number of Views Why automatically generated revocation requests do not add back revoked requests on a revocation date in RSA Identity Gove… Number of Views How users are selected for reviews that are triggered by rules 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
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme…
