Select Software Tokens for Provisioning

Document created by RSA Information Design and Development on Jun 13, 2017Last modified by RSA Information Design and Development on Jun 13, 2017
Version 2Show Document
  • View in full screen mode

When you select software tokens for provisioning, you are making specific types of software tokens available for users to request through the Self-Service Console. After requesting and receiving a software token, the user imports the token to an RSA SecurID application that resides on the user's computer or mobile device. The software token generates pseudorandom numbers (tokencodes), which are displayed in the application on the device.

Before a user can request a software token through the Self-Service Console, you must select this type of authenticator for user requests.

Before you begin 

You must add a software token profile before you can allow users to request software tokens. For instructions, see Add a Software Token Profile.

Procedure 

  1. In the Security Console, click Setup > Self-Service Settings.

  2. Under Provisioning, click Manage Authenticators.

  3. Under Software Token Profiles Available for Request, select the types of software tokens you want to make available for user requests.

  4. For each software token you select, do the following.

    1. The Display Name, Image Location, and Description fields are automatically populated and provide a display name, an image that displays in the Self-Service Console, and an application description.

    2. Confirm that the Tokencode Duration, Tokencode Length, Authentication Type, and Delivery Method information is correct.

    3. (Optional) In the Application Installation Download URL field, specify a URL link for users to download the installer for the specific software token application. Use this field only if your organization allows non-administrative users to install applications. If you leave this field blank, no URL link will be sent to the user in the request approval e-mail.

    4. (Optional) In the Device Help Document URL field, if you provide your own Help for the software token application, enter the URL for your Help file. If you leave this field blank, the user will not receive a URL link in the request approval e-mail.

    5. Select Make this the default option for software token requests if you want to make this token the default token type for software token requests.

    6. (Optional) Select Allow user to edit token attribute details if you wants users to be able to edit attributes associated with the software tokens that they request. For example, the user can give device serial number for device binding.

  5. (Optional) Under Token File Password Settings, select The user needs to provide the password, to protect the token file if you want to require users to create a password when they request a software token.

  6. Under Expiring Token Parameters, enter the number of days before a token expires that users can request a replacement token.

  7. Click Save.

 

 

Related Concepts

Workflow Policy

 

 


Attachments

    Outcomes