Distribute Multiple Software Tokens Using File-Based 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 distribute software tokens using file-based provisioning, token data is stored in a token distribution file (SDTID file). The SDTID file is added to a ZIP file for download.

Before you begin 

  • Instruct users to install the software token application on their devices. For installation instructions, see the Administrator's Guide for your software token application.

  • Add a Software Token Profile. Your Super Admin must add a software token profile.
  • Assign Tokens to Users

Note:  When you redistribute tokens using this method, any existing users of these tokens may no longer be able to authenticate. Users must import the new token data before they can authenticate.

Procedure 

  1. In the Security Console, click Authentication > SecurID Tokens > Distribute Software Tokens in Bulk > Generate Software Token Files.

  2. In the Job Name field, enter a name for the job, or accept the default name. The job is saved with this name so that you can review the details of the job later. Enter a unique name from 1 to 128 characters.

  3. From the Software Token Profile drop-down list, select a software token profile with file-based provisioning as the delivery method.

  4. In the DeviceSerialNumber field, do one of the following:

    • To bind the token to the device class, leave the default setting.

    • To bind the token to a specific device, clear the field and enter the device ID you obtained from the user.

  5. Enter a nickname or leave the Nickname field blank.

  6. You can choose to Password Protect the token file. The user must enter the password when adding the token to the SecurID application on the device. Select an option:

    • Password. Enter a password of your choice. This password applies to all software tokens in the token distribution file. A password can be up to 24 characters long for 128-bit tokens and 8 characters long for 64-bit tokens.

    • No password. The user does not enter a password.

    • User ID. The user enters his or her user ID.

    • Combination User ID followed by Password. The user enters his or her user ID and the password that you set. The user ID and password combination can be up to 24 characters long for 128-bit tokens and 8 characters long for 64-bit tokens.

  7. If you selected Password, enter the password in the Password and Confirm Password fields.

  8. Click Next.

  9. Enter the token selection criteria to find the tokens that you want to distribute. For example, enter the range of serial numbers for the tokens that you want to distribute.

  10. Click Next.

  11. Review the distribution summary and click Submit Job.

  12. Click the Completed tab to view completed jobs.

  13. From the context menu, click Download Output File.

  14. Save the output file to your machine.

  15. Safely deliver the token files to users.

 

 


Attachments

    Outcomes