RSA Authentication Manager 7.1 Administrator's Guide - IT Services ...

RSA Authentication Manager 7.1 Administrator’s Guide
After choosing individual or multiple distribution, do the following:
• E-mail the token file to the user.
• Instruct the user to download the token file to his or her device.
• Instruct the user to download the token application. The token application is
installed on the device, and displays the tokencodes on the device screen. Token
applications are available from the following URL:
http://www.rsa.com/node.asp?id=1313.
Installation instructions are included in the token application download kit.
Distributing Software Tokens Using Remote Token-Key Generation
(CT-KIP)
Note: Before distributing the software token, make sure that you have imported the
token records and assigned a CT-KIP-capable token to the user.
When you assign a CT-KIP-capable software token to a user, you can optionally select
to use remote token-key generation (CT-KIP) to deploy a token on user devices.
CT-KIP is more secure than other delivery methods because it enables Authentication
Manager and the device that hosts the software token, such as a web browser, to
simultaneously and securely generate the same token file on a device and the
Authentication Manager.
This allows you to put a token file on a user’s device without actually sending the
token file through e-mail or putting it on external electronic media. This greatly
decreases the chances that the token file will be intercepted by an unauthorized
person.
You need the following information when distributing software tokens using CT-KIP:
Software Token Device Type. The type of device on which the token is being
installed. An RSA SecurID Toolbar Token is an example of a software token
device type. You have to select the device type and enter information for the
device specific attributes.
You can add additional software token types to Authentication Manager. For more
information, see “Adding Additional Software Token Device Types to Your
Deployment” on page 120.
Device Nickname. The Device Nickname field allows a user to assign a
user-friendly name to the software token. For example, a user might name
software tokens “Office Token” or “Home Token” to differentiate between the
tokens he or she uses at home and the office.
Binding a Software Token to a Device. RSA software tokens include a
predefined field named Device Serial Number. When you issue the software
token to a user, you can enter the serial number of the device in this field, which
binds the issued token to the specific device with the corresponding serial number.
A token that is bound to a specific device cannot be installed on any other device.
84 3: Protecting Network Resources with RSA SecurID