RSA Security 6.1 Uživatelský manuál Strana 63

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 101
  • Tabulka s obsahem
  • ŘEŠENÍ PROBLÉMŮ
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 62
RSA SecurID Software Token 4.1 Administrators Guide
3: Provisioning Software Tokens 63
To configure Credential Manager to allow users to request a token:
1. On the Credential Manager Home page, under Token Provisioning, click
Manage Tokens.
2. On the Manage Tokens page, under Software Token Types Available for
Request, do one of the following:
If you installed a device definition file for RSA SecurID Software Token 4.1,
click Allow users to request Desktop PC 4.x software tokens or Allow
users to request Desktop Mac 4.x software tokens, as needed.
If you are using a device definition file for RSA SecurID Software Token 4.0,
click Allow users to request Desktop PC 4.0 software tokens or Allow
users to request Desktop Mac 4.0 software tokens, as needed.
The Display Name, Image location, and Description fields are automatically
populated with the application name, device image, and application description
that will be displayed to the user in the Self-Service Console.
3. In the Require User to Authenticate With field, do one of the following:
Click Passcode (PIN + tokencode) to require passcode authentication.
Click Tokencode only (PIN-less) to require tokencode authentication (no
PIN entry).
4. In the Supported Token Distribution Methods field, do one of the following:
To distribute tokens using Dynamic Seed Provisioning, click Generate
CT-KIP Credentials for Web Download. Leave the Client Application
URL field blank. Credential Manager automatically uses the CT-KIP URL
associated with RSA Authentication Manager 7.1.
To distribute tokens using SDTID files, click Issue Token File (SDTID).
5. (Optional) In the Make Default field, click Make this token type the default
option for token requests.
6. Leave the Device Help Document URL field blank.
The SecurID desktop application contains a built-in Help file.
7. (Optional) If you want the user to bind the token to a device attribute when the
user requests a token, in the Attribute Details field, select Allow users to edit
token attribute details.
If you selected the option to distribute tokens using SDTID files, you can require
the user to create a password to protect the token file.
8. (Optional) In the Token File Password field, select The user needs to provide
the password, to protect the token file.
If you select this option, when requesting a token using the Self-Service Console,
the user must create a password to protect the token file.
e
Zobrazit stránku 62
1 2 ... 58 59 60 61 62 63 64 65 66 67 68 ... 100 101

Komentáře k této Příručce

Žádné komentáře