RSA Security 6.1 Bedienungsanleitung PDF herunterladen (Seite 54)

RSA SecurID Software Token 4.1 Administrator’s Guide

54 3: Provisioning Software Tokens

8. Do one of the following:

• If you did not bind the token to the user SID, select System Generated Code.

The user will be prompted to enter the system-generated code in the SecurID

desktop application when importing the token.

• If you bound the token to the user SID, and you want to use the user SID as

the activation code, select DeviceSerialNumber. You must also set the

ActivationCode policy to 1 (true) and the CtkipUrl policy to the CT-KIP URL

to allow auto-import of the token. Auto-import is required because the user

SID exceeds the maximum number of characters that can be entered in the

application’s Enter Activation Code field. To set the ActivationCode policy,

see Appendix A, “Customizing the Application

.”

9. Click Next to view the token delivery details.

The Service Address field lists the URL of the CT-KIP provisioning server.

10. Do one of the following:

• If you selected a system-generated activation code, communicate the code to

the assigned user.

• If you did not set the CtkipUrl policy, communicate the URL listed in the

Service Address field to the assigned user.

Provisioning Tokens Using RSA Authentication Manager 6.1

RSA Authentication Manager 6.1 supports file-based provisioning. With file-based

provisioning, an XML file (SDTID file) containing token data is generated by

Authentication Manager when a software token is issued for an end user. RSA

recommends assigning a password to each SDTID file to protect the file in transit.

Password protection prevents an unauthorized person from using the token even if that

person is able to intercept the token file. You can distribute token files as attachments

to e-mail messages, or make the files available on a network directory or web site.

You can optionally use file-based provisioning in RSA Authentication Manager 7.1.

See “Using File-Based Provisioning in RSA Authentication Manager 7.1

” on page 60.

To use RSA Credential Manager for file-based provisioning, see “Provisioning Tokens

Using RSA Credential Manager” on page 61.

1 2 ... 49 50 51 52 53 54 55 56 57 58 59 ... 100 101

Keine Kommentare

RSA Security 6.1 Bedienungsanleitung Seite 54