
RSA SecurID Software Token 4.1 Administrator’s Guide
3: Provisioning Software Tokens 43
Fob-Style Software Tokens
Note: RSA Authentication Manager 7.1 and RSA SecurID Appliance 3.0 support
fob-style software tokens. RSA Credential Manager and RSA Authentication
Manager 6.1 do not support fob-style software tokens.
With fob-style software tokens, the user reads the SecurID tokencode from the
software token application. To authenticate, the user enters his or her user name and
the SecurID PIN into the SecurID protected application (for example, the VPN client),
followed by the SecurID tokencode. The combination of the PIN and tokencode forms
the OTP (passcode).
This authentication experience is similar to using an RSA SecurID hardware fob, such
as the SID700, where the user types the PIN in the protected resource, followed by the
current tokencode displayed on the fob. Because many users are familiar with RSA
hardware fobs, issuing fob-style software tokens can simplify the transition from
using a hardware fob to using a software token.
Fob-style software tokens used with the application can have a numeric PIN of 4 to 8
digits or an alphanumeric PIN of 4 to 8 characters.
The following figure shows the user authentication experience.
Comentarios a estos manuales