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

RSA Authentication Manager 7.1 Administrator’s Guide
Distributing Software Tokens By Token File (XML)
When you distribute software tokens by token file, you can e-mail the token file to the
user who can then download the file to install the token. Token files are in XML.
You need the following token information when distributing software tokens by token
file:
Note: Different token types require different sets of token information. Depending on
the type of token you are distributing, you might not need all of the information
described below.
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.
Software Token Selection Criteria. Know which tokens you want to distribute.
You can search by security domain, token file format, serial number, and other
token data.
Method for Issuing Software Tokens. You can select from the following
methods for issuing software tokens:
• Multiple tokens per file. Authentication Manager packs up all token records
into a single .sdtid file, and adds the .sdtid file to a .zip archive when it is
downloaded.
• One token per file. One software token record is written to an .sdtid file.
Enabling Copy Protection. The Enable Copy Protection option ensures that the
software token cannot be copied or moved from the directory in which it is
installed on a user’s computer or other device. By default, the Copy Protection
option is enabled. RSA strongly recommends that you use copy protection.
Note: Copy protection creates a system fingerprint of the user’s device and
associates this information with the software token. When a device is repaired
or upgraded, this information changes. Software tokens must be reissued if a
user’s computer hardware or device is repaired or upgraded.
82 3: Protecting Network Resources with RSA SecurID