Multi-Factor Authentication for the Imprivata Admin Console

Imprivata supports three authentication workflows to the Imprivata Admin Console: 

  • Legacy single-factor username and password authentication at the Imprivata Admin Console;

  • MFA authentication at the Imprivata Admin Console with username, OneSpan (VASCO) token passcode, and password/PIN — this is the workflow configured in this topic.

  • Single sign-on using SAML at the Imprivata Hub.

Imprivata supports the following combinations of these three workflows:

Legacy single-factor MFA at the Admin Console SSO at the Imprivata Hub Configuration required
Yes No No The default workflow. No setup required.
No Yes No Complete the configuration in this topic.
Yes No Yes

Do not complete the configuration in this topic. Complete the configuration in the topic SSO for the Admin Console instead.

No Yes Yes

Complete the configuration in this topic, and SSO for the Admin Console.

No No Yes

Do not complete the configuration in this topic. Complete the configuration in the topic SSO for the Admin Console instead, and complete the optional subsection Disable Local Authentication.

Login Screen States

The Imprivata Admin Console login screen changes depending on which workflows have been configured, as outlined above. This table describes what administrators see at the login screen for each configuration:

off-local-authentication IPM installed

SSO from Imprivata Hub

enabled

Tokens assigned to at least one admin

Login screen behavior
No No No Legacy username and password authentication only
No No Yes

The log in page shows a username field, a passcode field, and a Password/PIN field. SSO button does not appear.

No Yes Yes

The log in page shows a username field, a passcode field, and a Password/PIN field.

If SSO is enabled, the Log in with Imprivata Access Management SSO button also appears.
Yes Yes Yes

The log in page shows a username field, a passcode field, and a Password/PIN field.

If SSO is enabled, the Log in with Imprivata Access Management SSO button also appears.
Yes Yes No The login page shows Local authentication has been disabled and the Log in with SSO button.
Yes No No The login page shows Local authentication has been disabled. An error pop-up displays Authentication is not configured. Admins cannot log into the Imprivata Admin Console.
Yes No Yes

The log in page shows a username field, a passcode field, and a Password/PIN field. SSO button does not appear.

Import Tokens

To enable MFA directly on the Imprivata Admin Console, first import tokens for your administrators:

  1. In the Imprivata Admin Console, go to Devices > VASCO OTP Tokens.

  2. On the far right side of the console, select Import Tokens...

  3. In Import DPX File window:

    • Enter the shipping code that came with the token order;

    • Select whether the tokens are configured only for this application;

    • Browse to the DPX file.

  4. Click Upload.

    Imported tokens appear in the token list with a status of Available.

Assign Tokens

Assign tokens to administrators:

  1. In the Imprivata Admin Console, go to Devices > VASCO OTP Tokens.

  2. From the token list, click on an available serial number.

  3. On the VASCO OTP tokens properties page, go to Assignment Status > Assigned to and enter a username or choose a user. Use Assign Tokens... to assign several at once.

    BEST PRACTICE:

    Assign at least two tokens per administrator in case one is lost.

  4. Click Save.

    The token's status now includes the administrator name.

Enforce MFA Login

Install a special IPM to enforce MFA to the Imprivata Admin Console:

CAUTION:

Upload this IPM last: if no tokens are assigned and SSO with the Imprivata Hub is not enabled, the Admin Console login page shows "Authentication is not configured" and no one can sign in.

  1. Contact Imprivata Services and request the special IPM.

  2. On the Imprivata Appliance Console, go to Packages and upload the IPM.

  3. Upload and select Install IPM on all appliances.

    This IPM enforces MFA to the Imprivata Admin Console with username, VASCO token passcode, and password/PIN.

Expected Workflow

The token's detail page also shows whether the token shipped with a starter PIN, and whether that PIN must be changed the first time it is used. This determines the administrator's enrollment experience.

If The Token Already Has a PIN

  1. To log into the Imprivata Admin Console, go to the following URL:

    https://YourAddress/sso/administrator.html

  2. The log in page shows a username field, a passcode field, and a Password/PIN field.

  3. The administrator enters their username, generates a passcode from their token, and enters it along with their PIN.

  4. The administrator selects Log in

  5. The administrator is signed in. The Imprivata Admin Console opens. The token is now enrolled for all future sign-ins.

If The Token Has No PIN Yet, or The PIN Must Be Set

  1. To log into the Imprivata Admin Console, go to the following URL:

    https://YourAddress/sso/administrator.html

    The log in page shows a username field, a passcode field, and a Password/PIN field.

  2. The administrator clicks Reset PIN.

  3. On the Reset your PIN pane, the administrator enters their passcode, password, enters and confirms a new PIN, then selects Reset PIN.

  4. The Log in pane reopens with the success message PIN reset completed successfully.

  5. The administrator enters their username, generates a passcode from their token, and enters it along with their newly-reset PIN.

  6. The administrator clicks Log in

  7. The administrator is signed in. The Imprivata Admin Console opens. The token is now enrolled for all future sign-ins.