
RSA SecurID Software Token 4.1 Administrator’s Guide
48 3: Provisioning Software Tokens
Provisioning Overview
You can provision tokens for the SecurID desktop application using Dynamic Seed
Provisioning or file-based provisioning.
Use the information in the following table to become familiar with authentication
server requirements for token provisioning, and then click the link to see more
information on the provisioning method that you plan to use.
Provisioning Tokens Using Dynamic Seed Provisioning
Dynamic Seed Provisioning (also called Remote Token Key Generation) uses the
RSA Cryptographic Token Key Initialization Protocol (CT-KIP) for the secure
initialization and configuration of cryptographic tokens. When the protocol is
executed, it results in the generation of the same shared secret on both the server and
the token. You do not need to send a token file over the network to the remote user.
To use Dynamic Seed Provisioning, you configure and issue a token in
RSA Authentication Manager 7.1, selecting CT-KIP as the method used to distribute
the token. You must also specify a special code, called an activation code, that the user
must enter to activate the token. The activation code can contain up to 25 characters.
For more information, see “Distribute the Token
” on page 53.
Provisioning
Method
Server Requirement Reference
Dynamic Seed
Provisioning
RSA Authentication Manager 7.1
RSA SecurID Appliance 3.0
“Provisioning Tokens Using Dynamic Seed
Provisioning” on page 48
File-Based
Provisioning
(SDTID files)
RSA Authentication Manager 6.1
RSA Authentication Manager 7.1
RSA SecurID Appliance 3.0
“Provisioning Tokens Using RSA Authentication
Manager 6.1” on page 54
“Using File-Based Provisioning in RSA
Authentication Manager 7.1” on page 60
Dynamic Seed
Provisioning or
File-Based
Provisioning
RSA Credential Manager
“Provisioning Tokens Using RSA Credential
Manager” on page 61
Komentarze do niniejszej Instrukcji