Face Recognition as an Authentication Method
Imprivata MDA supports face recognition as an authentication method.
Assumptions
The configuration tasks in this topic assume that:
-
You already have enabled Imprivata MDA in your enterprise, deployed mobile app profiles, and configured the Mobile Policy and user authentication for mobile devices.
For more information, see Enable Imprivata MDA and Deploy Profiles and Configure the Mobile Policy and User Authentication.
-
You have not already configured face recognition as an authentication method for desktop access using Imprivata Enterprise Access Management.
For more information, see the Imprivata Enterprise Access Management online help.
Requirements
-
You must sign a Cloud Services Amendment to use face recognition authentication in a production environment.
-
The Imprivata Cloud Connect service to your tenant on the Imprivata Cloud Platform must be up and running.
-
Users in a policy enabled for face recognition must be synced from Active Directory (AD) to Entra ID.
-
The cloud must be synced from AD to Entra ID with Entra Connect.
-
Each user in scope for the facial recognition workflow must exist within Entra ID and each user must also be allocated a P1 or higher Microsoft license.
-
Internet access is required for facial biometric authentication.
If the device cannot connect with your Imprivata Cloud Platform, an error message will appear during authentication. In this scenario, the user can select another authentication method (password / Imprivata PIN, etc) to complete the authentication.
-
Imprivata Licensing: Face recognition authentication requires an Authentication Management license and a Confirm ID for Remote Access license, in addition to your Imprivata MDA licenses. For more information, see Imprivata Licensed Features.
-
Face recognition requires camera permission to be granted on the device.
If you add the AppConfig flag requireCameraPermission, the camera permission is handled along with other permissions upon Imprivata MDA first run.
Imprivata MDA also checks whether the permission is granted before starting camera for face recognition. If the permission is not granted, Imprivata MDA prompts the user to grant it.
Considerations
Consider the following information for this feature:
-
Face recognition is not supported with offline mode.
-
Biometric data is not stored on the device.
-
Supports face masks.
BEST PRACTICE:To ensure the highest quality possible, the initial enrollment of a user's face should be done without a mask.
Subsequent authentications can be done with a mask.
-
Imprivata MDA face recognition is not supported for the Epic Rover witness authentication workflow in this release.
Before You Begin
Face recognition authentication for Imprivata MDA requires:
-
The Imprivata appliances in your Imprivata enterprise must be running Imprivata Enterprise Access Management 25.3 or later.
For more information on upgrading your Imprivata appliances, see the Imprivata Upgrade portal.
-
Complete the connection between your Imprivata enterprise and your tenant on the Imprivata Control Center. See Secure Connection to Imprivata Cloud Platform.
-
Imprivata MDA 8.0 or later.
Secure Connection to Imprivata Cloud Platform
Configure the secure connection between your Imprivata appliances and the Imprivata Cloud Platform. To confirm whether this connection is complete, on the Imprivata Admin Console, see the Status panel on the right-hand side. Look for a green checkmark icon for Access Management integration.
Imprivata Access Management Setup
Contact Imprivata Services. Services will create a Cloud Tenant for your enterprise, and send a Welcome email with a link to the Imprivata Access Management Setup. Click the link in the email and follow the prompts to complete the secure connection.
Before You Begin
-
You need access to your Imprivata Admin Console.
-
Optional — a PNG, JPG, or GIF of your organization logo (200 x 100 pixels or smaller, max 100KB).
Imprivata Access Management Setup supports several Imprivata products on the Imprivata Cloud Platform.
Some steps may require information from the Imprivata Admin Console or your identity provider (IdP) console.
Some steps may not be required for configuring Imprivata MDA.
Network Requirements
Ensure that your firewall policy is configured to allow communication between the Imprivata appliances and the production Imprivata Cloud Platform.
Add the following hosts to your firewall allowlist:
-
*.sys.imprivata.com
-
*.app.imprivata.com
For non-US regions, replace the .com with the appropriate domain suffix for your region, for example, *.sys.imprivata.uk.
By default, the Imprivata Cloud Connect service is disabled. You must enable the service before configuring the connection to the Imprivata Cloud Platform.
To start the service:
-
In the Imprivata Appliance Console, go to System > Operations.
-
Locate Imprivata Cloud Connect, and click Stop/restart options.
-
Select Restart Imprivata Cloud Connect on all appliances, and click Go.
Using the Imprivata Admin Console, copy your enterprise integration ID. You require this value to use the Imprivata Access Management setup to create an integration token.
To copy your integration ID:
-
In the Imprivata Admin Console, click the gear icon > Imprivata Access Management integrations.
NOTE:A status message of Unable to verify integration. Unable to connect to Imprivata Access Management is expected.
-
Copy the enterprise integration ID to your clipboard.
-
Do not log out. You finish configuring the connection here after using the Imprivata Access Management setup to create the integration token.
Using the Imprivata Access Management setup, enter your enterprise integration ID to create an integration token. This token is required to finish configuring the connection in the Imprivata Admin Console.
To create the integration token:
-
Open the Imprivata Access Management setup.
-
If you have not already, agree to the Cloud Features Agreement and enter information about your organization.
-
Go to the Connect to Enterprise Access Management screen, and paste the integration ID into Enterprise integration ID.
-
Click Create integration token and copy it.
-
Return to the Imprivata Admin Console to finish configuring the connection.
Using the Imprivata Admin Console, finish configuring the connection to the Imprivata Cloud Platform using the integration token you created.
To finish the configuration:
-
In the Imprivata Admin Console, click the gear icon > Imprivata Access Management integrations.
-
Paste the integration token, and click Integrate.
-
Select Administrator console single sign-on using SAML.
This setting is required to enable SSO access to your administrator consoles in the Imprivata Access Management portal.
-
To configure the integration with Entra ID as the IdP, continue here: Configure Entra ID as the Identity Provider
-
To configure the integration with a different IdP, continue here: Configure the Identity Provider
Configure Entra ID as the Identity Provider
Use the Imprivata Access Management setup to create the Imprivata SP metadata file. You require this file when configuring the Entra ID enterprise application.
To create the metadata file:
-
Open the Imprivata Access Management setup.
-
Agree to the Cloud Features Agreement and enter information about your organization.
-
Skip to the Identity Provider Connect screen.
-
Copy the Imprivata SP metadata URL, paste it into a new browser tab, and save the page as an XML file.
Do not close the setup. You finish configuring the connection here after you configure the enterprise application.
An Entra ID enterprise application is required to allow SAML-based SSO to the Imprivata Access Management portal.
To configure the enterprise application:
-
From the Azure portal, go to Microsoft Entra ID.
-
Click Manage > Enterprise Applications > New application.
-
Click Create your own application.
-
Enter a name for the application, select Integrate any other application you don't find in the gallery, and then click Create.
-
From the Overview page, click Assign users and groups, and then add the Imprivata admin user group.
-
Go to the Overview page, click Set up single sign-on, and then select SAML.
-
Click Upload metadata file, and upload the Imprivata SP metadata file you created previously.
-
Under Basic SAML Configuration, click Edit, and enter the following Sign on URL:
https://access.imprivata.com. -
Save the settings.
Copy and save required federation and group attribute values from the enterprise application. You will use these values to complete the SAML configuration and specify the Imprivata admin group.
To locate the required values:
-
Go to SAML certificates, and copy the App Federation Metadata URL.
-
Under Attributes & Claims, click Edit, and copy the claim name for the user groups value.
Example:
http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsNOTE:If the user group claim does not exist, create it. When creating it, select Groups assigned to the application and use Group ID as the source attribute.
-
Return to the Microsoft Entra ID Overview page.
-
Click Manage > Groups >All groups.
-
Locate the admin group and copy its object ID.
Return to the Imprivata Access Management setup to finish the configuration.
With the federation and group attribute values you had previously saved, use the Imprivata Access Management setup to finish the SAML configuration and specify the Imprivata admin group.
To finish the configuration:
-
Open the Imprivata Access Management setup, and return to the Identity Provider Connect screen.
-
Enter your organization's domain and a user-friendly display name.
-
Enter the SAML IdP metadata URL from the enterprise application, and click Continue.
-
Enter the user group claim name in to SAML attribute name.
-
Enter the object ID of the admin group in to SAML attribute value, and click Continue.
If you are specifying multiple admin groups, the object IDs must be comma-separated.
-
Click access.imprivata.com to log in to the Imprivata Access Management portal.
Specifying a metadata URL allows for easier maintenance. The system automatically polls the URL at regular intervals.
This ensures that your IdP configuration stays up to date with the latest metadata, such as certificate changes.
If you upload a metadata file instead, the system does not update it automatically. From the Imprivata Access Management portal, you must edit the configuration to replace the file manually or switch to a URL.
To add the trusted Imprivata IP addresses:
-
From the Azure portal, go to Microsoft Entra ID, and select > Manage > Security > Manage > Named locations.
-
Click IP ranges location.
-
Enter a name for the new location, and then select Mark as trusted location.
-
Add the following IP addresses:
-
44.207.16.175/32 -
44.196.189.191/32 -
34.195.47.118/32
-
-
Click Add, and then Create.
If per-user multifactor authentication is enabled for users, adding the trusted Imprivata IP addressees to the list of MFA trusted IPs is required.
To add the IP addresses:
-
From the Microsoft Azure Portal, go to Microsoft Entra ID > Manage > Users, and click Per-user MFA.
-
Select the Service Settings tab.
-
Add the following IP addresses to Skip multifactor authentication for requests from following range of IP address subnets:
-
44.207.16.175/32 -
44.196.189.191/32 -
34.195.47.118/32
-
-
Click Save.
By default, Microsoft Entra Connect Sync pass-through authentication or Password Hash Sync (PHS) is supported.
If your Entra ID environment is federated with a third-party IdP, however, PHS is required.
To verify if PHS is enabled:
-
From the Microsoft Azure Portal, go to Microsoft Entra ID > Manage > Microsoft Entra Connect.
-
Click Connect Sync.
-
Under Microsoft Entra Connect sync, verify that Password Hash Sync is enabled.
-
If it is not enabled, configure Password Hash Synchronization from the server where the Microsoft Entra Connect Sync Agent is installed.
Configure Imprivata Enterprise Access Management as a directory. Doing so, provides full user sync capabilities.
Syncing your users requires one of the following:
-
Entra ID Global Administrator rights
-
Privileged Role Administrator rights
To sync Entra ID users:
-
Log into the Imprivata Access Management portal (access.imprivata.com).
-
Click the gear icon > Users > Entra ID users.
-
Click Add an Entra ID directory now.
-
Enter your Entra ID Tenant ID, and click Continue to Microsoft Authentication.
-
Using an Entra ID Global Administrator account, or another account with privileges to grant admin consent for application permissions, log in to Entra ID.
-
When prompted, review the required permissions, and click Accept.
-
Click Specify groups now. Enter one or more groups names, and click OK.
-
Click Update now to sync users.
If your Entra ID environment is federated with a third-party IdP, this step is required.
The Imprivata Cloud Platform must be able to validate user passwords when entered. In a federated environment, Imprivata needs to avoid these calls from being redirected to the federated identity provider (IdP). You must change the home realm discovery policy for authentication from the Imprivata Cloud to your Entra ID tenant only. This only applies to authentication calls made by the Imprivata Access Management Sync.
To create and apply the Home Realm Discovery policy:
-
Log in to Microsoft Graph Explorer.
To make it more secure, log in as the Global Administrator.
-
Consent to the Microsoft Graph explorer application in your tenant.
For more information, see the Microsoft Graph API documentation.
-
Create a home realm discovery policy by making the following HTTP request:
POST - https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPoliciesRequest body
In the request body, supply a JSON representation of the homeRealmDiscoveryPolicy object:
Copy{
"displayName": "yourPolicyName",
"definition": [
"{\"HomeRealmDiscoveryPolicy\":
{\"AllowCloudPasswordValidation\":true, } }"
],
"isOrganizationDefault": false
}Response
If successful, this method returns a
201 Createdresponse code and a new homeRealmDiscoveryPolicy object in the response body.Example Response
Copy{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#policies/homeRealmDiscoveryPolicies",
"value": [
{
"id": "239cbead-1111-654a-9f50-1467d691aaa",
"deletedDateTime": null,
"definition": [
"{\"HomeRealmDiscoveryPolicy\" : { \"AllowCloudPasswordValidation\":true, } }"
],
"displayName": "Exclude Federated Authentication ",
"isOrganizationDefault": false
}
]
} -
Assign the home realm discovery policy to the Imprivata Access Management Sync application by making the following HTTP request:
POST - https://graph.microsoft.com/v1.0/servicePrincipals/<the Imprivata Access Management Sync application object id>/homeRealmDiscoveryPolicies/$ref
Request body
In the request body, supply the identifier of the homeRealmDiscoveryPolicy object that should be assigned.
Copy{
"@odata.id":"https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPolicies/<yourHomeRealmDiscovery_PolicyID>"
}Response
If successful, this method returns a
204 No Contentresponse code. -
Verify that the home realm discovery policy was successfully applied to the service principal by making the following HTTP request:
GET - https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPolicies/<homeRealmDiscoveryPolicy object id>/appliesTo
Response
Copy{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#directoryObjects",
"value": [
{
"@odata.type": "#microsoft.graph.servicePrincipal",
"id": "c1f8e0d4-25b0-46b2-aaa8-827822631a33",
...
You must exclude the Imprivata Access Management Sync application from all conditional access policies that would require MFA for Imprivata users.
Microsoft-managed policies don't allow you to exclude specific cloud apps. If you have a Microsoft-managed policy that requires MFA, recreate it so you can exclude the Imprivata Access Management Sync app, and then turn off the Microsoft-managed policy.
To update a conditional access policy:
-
From the Microsoft Azure Portal, go to Microsoft Entra ID, select Manage > Security > Protect > Conditional Access > Policies.
-
Click the policy that applies to your Imprivata users.
-
Under Target resources, click All resources (formerly All Cloud apps).
-
Click Exclude, and then toggle Select resources.
-
Under Select specific resources, click None or any of the listed applications.
-
Search for Imprivata Access Management Sync, select it, and click Select.
-
Save the policy.
-
Repeat for all conditional access policies that would require MFA for Imprivata users.
Configure the Identity Provider
You can choose any SAML IdP to provide authentication (e.g., Okta, Ping ID). In the Cloud Tenant Setup Wizard, on the Identity provider: Connect page, configure the connection between your identity provider and Imprivata Access Management.
To configure your IdP:
-
Open the Imprivata Cloud Tenant Setup wizard.
-
If you have not already, agree to the Cloud Features Agreement and enter information about your organization.
-
Go to the Identity Provider Connect screen.
-
Copy the Imprivata SP metadata URL and provide it to your IdP. When configuring the IdP's application:
-
Specify
https://access.imprivata.comfor the single sign-on URL. -
Recommended: configure email address as the NameID format for user identity.
-
Recommended: configure Group ID (rather than group name) as the source attribute for group claims.
-
-
Enter the SAML IdP metadata URL, and click Continue.
-
Enter the SAML name/value pair that identifies users with administrative access, and click Continue.
-
Click Go to Access URL: access.imprivata.com to test the authentication workflow to access Imprivata Access Management.
Enterprise Access Management User Policy Setup
-
In the Imprivata Admin Console, go to the User policies page > Authentication tab > Desktop Access authentication section.
-
Select Face recognition as a primary factor.
-
Select a second factor for Face recognition:
-
No second (not recommended)
-
In EAM 25.4 and later, the no second factor option has been removed.
-
In EAM 25.3, the Imprivata Admin Console still displays the option for no second factor. It is not a recommended configuration.
-
-
Imprivata PIN
-
Password
-
Proximity Card
-
Security Key
BEST PRACTICE:For enhanced protection against sophisticated attacks, pair Face authentication with a strong second factor like proximity card or security key.
-
-
Select another primary factor.
For example, if users in this policy must use a different authentication method when Face recognition authentication is not available.
-
Specify the grace period for authentication:
-
In EAM 25.3 and later, in the Authentication method options section > Face recognition, specify the grace period in the Grace period for second factor after face recognition boxes, up to 24 hours 59 minutes.
-
-
Click Save.