Allow a User to Authenticate Without an RSA SecurID PIN
RSA Authentication Manager supports authentication with tokens that do not require an RSA SecurID PIN. To authenticate, instead of entering the PIN followed by the tokencode, the user enters just the tokencode displayed on the token.
Authenticating with just a tokencode is ideal for situations such as software tokens on smart cards that users have to unlock with a PIN or on desktops that users must unlock with a password. In these situations, the PIN or password that unlocks the resource is one of the authentication factors, and the tokencode serves as the second.
You can configure both hardware and software tokens so they do not require a PIN for authentication. You must notify users if you make any change in the user authentication requirement options.
You can perform this procedure for one user or more users.
Procedure
In the Security Console, click Authentication > SecurID Tokens > Manage Existing.
Use the search fields to find the tokens that you want to configure.
Select the checkbox next to the tokens that you want to configure.
From the Action menu, click Don't Require SecurID PIN.
Click Go.
Related Concepts
Related Articles
Allow a User Group to Authenticate on an Agent 35Number of Views Allow Users to Authenticate on an Agent 24Number of Views Set a Temporary On-Demand Tokencode PIN for a User 49Number of Views syslog over TCP 223Number of Views Clear an RSA SecurID PIN in the User Dashboard 41Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle 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