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
Use the User Dashboard to Require PIN Changes Number of Views 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 Require Password Change at Next Logon 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
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
