SAML Settings

The SAML configuration enables administrators to configure SAML fo to enable Single Sign On (SSO) option. When administrators use SAML to configure SSO, the configuration immediately changes the authentication methods for the server.

IMPORTANT:
The SAML configuration may change the authentication method at a server-level and the change is immediate. Imprivata recommends that you follow this procedure in a scheduled maintenance session to prevent down-time for your users.
TIP:
Create a local administrator to maintain access to your server in case the configuration locks you out. Remember to contact Imprivata Customer Service if you encounter any problems.

This document contains the requirements and step-by-step guide on how administrators set up SAML to configure SSO.

Requirements

To complete the configuration ensure that you meet the following requirements. If these requirements are not met, the configuration will fail and you risk down-time for your users.

  • Permissions and Access

    • You must be an administrator at server-level to access to the SAML configuration page.

    • You must have access to your Identity Provider (IdP) configuration.

  • Authentication Methods

    • Your Identity Provider (IdP) must be able to request MFA to your users.

  • Server Version:

    • Your server must be version 23.1.12 or higher. Find your version at the footer of your server's Administrator Console.
      Contact success@imprivata.com to receive assistance in updating your server.

Failing to meet these requirements results in errors during the configuration.

Step-by-Step Guide

The SAML configuration occurs in the following stages:

  1. Download your server's data.

  2. Upload your server's XML to your Identity Provider (IdP).

  3. Configure SSO in your server.

    NOTE:

    Imprivata VPAM now automatically update Azure Entra ID (formerly Azure Active Directory) SAML signing certificates during key rollovers. This automation removes the need for manual certificate updates. The system also supports multiple active certificates to ensure continuous SSO authentication during transitions.

  4. Finalize the configuration.

Each step is its own process and administrators must follow each one properly to secure the configuration.