Configuring External OTP Tokens

Sites that have deployed Secure Computing SafeWord or RSA Security SecurID strong authentication tokens can leverage these existing investments. Imprivata includes built-in RADIUS integration to Secure Computing’s Premier Access and Remote Access Servers and RSA's Authentication Manager for token authentication. Imprivata can provide a seamless single-step desktop login using two-factor one-time passcodes for logging in to any SSO-enabled client/server, web, or legacy application from any Imprivata-enabled desktop. ID token-enabled users authenticating to Imprivata use their domain usernames instead of their ID token system usernames (these may be the same values). In all other ways Imprivata makes no changes to the user experience.

CAUTION:

When configuring external OTP tokens that are allowed for e-prescribing controlled substances, you are required to attest that the OTP token server is FIPS-compliant and that OTP tokens are properly enrolled per DEA EPCS regulations. This action is logged in the Imprivata audit records. FIPS 140-2 Level 1 compliant tokens are required when used to e-prescribe controlled substances. See Configuring External OTP Tokens for more information.

NOTE: If you are transitioning from RSA SecurID or Secure Computing SafeWord tokens to VASCO Digipass tokens, you can use both SecurID or SafeWord and OneSpan (previously VASCO) OTP tokens in the same Imprivata system.

NOTE: The names OneSpan and VASCO may be used interchangeably in Imprivata documentation and in the Imprivata Admin Console interface.

There are two steps to configuring the Imprivata appliance to work with an ID token server:

  1. Configuring the ID Token Server to Recognize the Imprivata Appliance.

  2. Configuring the Imprivata Appliance to Recognize the ID Token Server

Supported External OTP Tokens

Imprivata supports the following external OTP tokens:

  • RSA ID® tokens with RSA Authentication Manager®

  • Secure Computing SafeWord® tokens with PremierAccess® and RemoteAccess™ servers

  • External RADIUS hosts, including PhoneFactor (PhoneFactor tokens cannot be used for Enterprise Access Management with MFA workflows.)

Configuring the ID Token Server to Recognize the Imprivata Appliance

Follow the procedure specific to the type of external OTP token you are enrolling.

Authenticating to Enterprise Access Management with OTP Tokens

Authenticating to Enterprise Access Managementwith OTP tokens differs slightly depending on the type of ID token you are using.