Managing OneSpan (VASCO) OTP Tokens

Imprivata provides support for VASCO (now known as OneSpan) OTP tokens out-of-the-box. Imprivata embeds VASCO's VACMAN middleware and management components within the Imprivata appliance. There is no separate token management server to purchase or maintain.

You can manage VASCO OTP tokens on the VASCO OTP tokens page of the Imprivata Admin Console (Devices menu > VASCO OTP tokens)

Tasks related to managing individual tokens, including assigning available tokens, are described in Managing an Individual OneSpan (VASCO) OTP Token.

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 OneSpan OTP tokens, you can use both SecurID or SafeWord and OneSpan OTP tokens in the same Imprivata system.

This topic includes instructions on managing OneSpan OTP support.