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 11Number of Views Require Password Change at Next Logon 20Number of Views Require Users to Change Their RSA SecurID PINs 21Number of Views Require a User to Change a Password using the User Dashboard 113Number of Views Error 25000.Upgrade error: unable to migrate sdserv database(3) 40Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Report preview and/or generation fails with 'java.lang.NoClassDefFoundError: Could not initialize class net.sf.jasperrepor… RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide How to set up the REST RSA SecurID Authentication API for Authentication Manager 8.2 SP1