Assign and Distribute a Software Token to a User Using Dynamic Seed Provisioning in the User Dashboard
Before a user can use a software token to authenticate, you must assign and distribute the token to the user. 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.
AM provides dynamic seed provisioning, which uses the Cryptographic Token Key Initialization Protocol (CT-KIP) to generate token data without the need for a token file. After you complete the provisioning steps, AM displays the URL link of the CT-KIP server and the token activation code. You need these two pieces of information in order to deliver the token to a device as a URL.
Before you begin
Confirm the following:
- Software tokens have been imported.
- Software token profiles have been added.
Procedure
In the Security Console, go to the Home page.
Use Quick Search to find the user.
Select the user to whom you want to assign a token.
Under Assigned SecurID Tokens, click Assign More Tokens > Assign Software Tokens.
- Select a token from the list or search for a token in the search bar.
- Click Assign Token(s).
- From the Select Token Profile drop-down list, select a software token profile with dynamic seed provisioning as the delivery method.
After you finish
Use dynamic seed provisioning to deploy a software token on a user's device. For instructions, seeDistribute One Software Token Using Dynamic Seed Provisioning.
Related Concepts
Related Articles
Distribute One Software Token Using Dynamic Seed Provisioning 100Number of Views Distribute One Software Token Using Dynamic Seed Provisioning 273Number of Views Token seed import fails with 'Import Token failure' error for RSA Authentication Manager 611Number of Views Assign a Hardware Token to a User 85Number of Views New Delivery Method for Token Seed Records 100Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators