RSA Security 6.1 Bedienungsanleitung Seite 87

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 101
  • Inhaltsverzeichnis
  • FEHLERBEHEBUNG
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 86
RSA SecurID Software Token 4.1 Administrators Guide
A: Customizing the Application 87
You can automate the provisioning of one token to a user using CT-KIP by setting
both the ActivationCode and the CtkipUrl policies. Set ActivationCode to 1, and set
CtkipUrl to the URL of your CT-KIP server. The first time that the user starts the
desktop application, the token is automatically imported, as long as one of the
following conditions is met:
The user does not already have a token.
All of the tokens in the users token database have expired.
Note: Because the ActivationCode policy does not apply to Mac OS X desktops, you
cannot automatically import a token using CT-KIP in a Mac OS X implementation.
CtkipUrl
By default, when importing a token using CT-KIP, the user must enter the URL of the
CT-KIP server and must enter the activation code on the Import from Web screen. If
you do not want the user to have to enter the URL, set the CtkipUrl policy. This
prefills the Enter URL field, and the user then needs to enter only the activation code.
On Windows desktops, you can automate the provisioning of one token to a user by
setting both the CtkipUrl policy and the ActivationCode policy, as described in the
previous section.
DisableChangeTokenName
By default, users can change the nicknames of their tokens. If you set nicknames on
users’ tokens when you issue them in Authentication Manager, and you do not want
users to change the nicknames, set the DisableChangeTokenName policy. This
removes the Change Name option from application user interface.
Seitenansicht 86
1 2 ... 82 83 84 85 86 87 88 89 90 91 92 ... 100 101

Kommentare zu diesen Handbüchern

Keine Kommentare