Assign Hardware Tokens to Multiple Users
Before users can use hardware tokens to authenticate, you must assign the tokens to the users. You can assign up to three hardware or software tokens to a single user. Tokens that are managed in Cloud Access Service (CAS) do not count towards the three token limit.
You can run a command-line utility that restricts the number of tokens that can be assigned to a user. For instructions, see Restrict the Number of Active Tokens per User.
Before you begin
Procedure
In the Security Console, click Identity > Users > Manage Existing.
Use the search fields to find the users to whom you want to assign tokens.
From the search results, select the checkboxes next to the users to whom you want to assign tokens.
From the Action menu, click Assign SecurID Tokens.
Click Go.
From the list of available RSA SecurID tokens, select the checkbox next to the hardware tokens that you want to assign.
Note: The number of selected tokens must equal the number of selected users.
Click Assign.
After you finish
Distribute the hardware tokens:
- If users are located within close proximity, instruct the users to physically collect the tokens.
- If your organization is large and geographically dispersed, distribute tokens by mail.
Related Concepts
Related Articles
CyberArk Authentication fails when using hardware tokens 22Number of Views Assign a Hardware Token to a User 93Number of Views Assign Software Tokens to Multiple Users 74Number of Views Transfer SecurID 700 Hardware Token Ownership to Cloud Access Service 345Number of Views Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… 2.4KNumber of Views
Trending Articles
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 How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle