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 Trusted Users to Authenticate Using RSA RADIUS 9Number of Views How to require users to use SecurID to authenticate on some clients and ACE/Server passwords on other clients. 9Number of Views Allow Users to Authenticate on an Agent 23Number of Views Web Service command updateReviewItems does not allow only comments for review items to be changed in RSA Identity Governan… 28Number of Views Remote Desktop Protocol Vulnerability MS12-020 16Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x