Face Recognition — EPCS Desktop
Imprivata Enterprise Access Management supports Face recognition authentication for EPCS workflows on the desktop, and also:
-
Mobile EPCS Authentication
Overview
The following configurations are required for Face Recognition. If you have already enabled Face Recognition for another EAM workflow, these steps do not need to be repeated; you only need to configure the EPCS workflows within workflow policy.
-
Configure an identity provider (IdP) to authenticate users to the Imprivata Hub.
-
Configure a connection to the Imprivata Cloud Platform.
-
If using an integration to Entra ID, sync your users with the Imprivata Cloud Platform.
After configuring Entra ID and syncing users with the Imprivata Cloud Platform, verify that the users exist in the Imprivata Hub (access.imprivata.com).
-
Imprivata EAM also uses SCIM (System for Cross-domain Identity Management) to integrate with Active Directory and other non-Entra tenants to synchronize Imprivata EAM and the Imprivata Cloud Platform.
Requirements
-
Face recognition authentication requires an Authentication Management license and a Remote Access license.
-
Internet access is required for face recognition authentication. If the endpoint cannot connect with your Imprivata Cloud Platform, an error message will appear during authentication. The connection between the endpoint and your Imprivata appliance is not required.
-
A 1080p camera must be installed and enabled at the endpoint computer. Modern cameras capable of handling Zoom video conferencing are sufficient.
Configure an IdP to authenticate users to the Imprivata Hub
Configuring an IdP is required to authenticate administrators to the Imprivata Hub. You need access to theImprivata Hub to synchronize your Entra ID users with the Imprivata Cloud Platform.
If you have already configured access to the Imprivata Hub, you can skip this step.
You can configure:
-
Imprivata to function as an internal IdP.
-
Doing so creates a tenant-specific identity directory with a local administrator, which provides quick access to the Imprivata Hub without the need for an external IdP.
-
After configuring Imprivata as the IdP, you can configure an external IdP at any time.
-
-
Any external third-party IdP. For example, Microsoft Entra ID.
-
Configuring an external IdP lets you use your organization’s existing identity infrastructure to authenticate administrators.
-
Configuring Entra ID as an IdP has the added benefit of letting your non-administrative users enroll their face as an authenticator using My Imprivata Identity from any device. Unlike other enrollment methods, My Imprivata Identity does not require access to an endpoint where the Imprivata agent is installed.
-
To configure Imprivata Directory:
-
Open the Imprivata Access Management setup.
-
Agree to the Cloud Features Agreement and enter information about your organization.
-
Skip to the Imprivata Identity Provider Connect screen.
-
Enter a domain for the Imprivata Directory.
NOTE:The domain name must be unique and cannot be reused across multiple tenants.
-
Enter a username and password for the initial administrator, and note the complete Imprivata username, which includes the Imprivata Directory domain
You require the complete username to log in to the Imprivata Hub.
-
Skip to the You're ready to go screen, and click the link to log in to the Imprivata Hub.
Requirements
-
Users in a policy enabled for Face Recognition must be synced from Active Directory (AD) to Entra ID.
-
The endpoint computers can be AD-only, as well as the Entra ID configurations described here.
-
Users must be synced from AD to Entra ID with Entra Connect, Entra Cloud Sync, or maintained directly in Entra ID.
-
Each user in scope for the Face recognition workflow must exist within Entra ID, and each user must also be allocated a Microsoft Entra ID license P1 or higher.
You require access to the following to complete the configuration:
-
The Imprivata Access Management setup.
-
The Microsoft Entra Admin center.
Save the Imprivata Service Provider Metadata
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.
Configure the Entra ID App
An Entra ID enterprise application is required to allow SAML-based SSO to the Imprivata Hub.
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 Entra App Values
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.
Use the Entra App Values 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 Hub.
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 Hub, you must edit the configuration to replace the file manually or switch to a URL.
The following are generic steps to configure any external third-party IdP to authenticate users to the Imprivata Hub. For example, these steps apply to Ping Identity and Okta.
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.
Configure the Connection to the Imprivata Cloud Platform
Enabling Face recognition requires a connection to the Imprivata Cloud Platform. You need the following to complete the configuration:
-
Access to the Imprivata Appliance Console.
-
Access to the Imprivata Admin Console.
-
Optional — a PNG, JPG, or GIF of your organization logo (200 x 100 pixels or smaller, max 100KB).
If you have already configured a connection to the Imprivata Cloud Platform, you can skip this step. To determine if a connection has already been configured, log into the Imprivata Admin Console. The Status panel includes connection information. A green check mark for Access Management integration indicates a connection has been configured.
Add the Required Hosts to Your Firewall Allowlist
Ensure that your firewall policy is configured to allow:
-
Communication between the Imprivata appliances and the production Imprivata Cloud Platform.
-
Communication between your endpoints and the production Imprivata Cloud Platform.
Add the following hosts to your firewall allowlist:
-
<tenantID>.sys.imprivata.com
-
astra.sys.imprivata.com
-
<tenantID>.access.imprivata.com
-
access.imprivata.com
-
metadata.app.imprivata.com
-
file-access.app.imprivata.com
-
idp.app.imprivata.com
Consider the following:
-
For non-US regions, replace the
.comwith the appropriate domain suffix for your region, for example,*.sys.imprivata.eu. -
You can locate your Imprivata Cloud Platform tenant ID by clicking the link to the Imprivata Access Management setup in the welcome email. The tenant ID appears in the URL. For example:
Certificate Revocation Checking and Outbound Communication on TCP Port 80
Imprivata cloud services rely on standard TLS certificate validation performed by the client platform. Depending on the operating system, browser, connector, application, and local security policy, certificate validation may include revocation checking for the TLS certificates used to establish trusted connections. During certificate validation, the client may retrieve certificate revocation information from the issuing Certificate Authority (CA)."
The location of this information is published in the certificate itself:
-
The CRL Distribution Points (CDP) extension names where the Certificate Revocation List (CRL) can be downloaded
-
Where applicable, the Authority Information Access (AIA) extension names the OCSP responder that can be queried for a certificate's status.
The revocation data itself is not carried in the certificate; the client uses these pointers to fetch it from the CA's endpoints.
Some of those CA revocation endpoints are published as HTTP URLs and therefore require outbound access over TCP port 80.
-
This port 80 access is used only to retrieve CA-published certificate status information (CRLs or OCSP responses).
-
It is separate from the encrypted application connection to Imprivata cloud services, which uses HTTPS/TLS.
Administrators who restrict outbound HTTP traffic should allow outbound TCP port 80 only from the systems that connect to Imprivata cloud services, and only to the CA revocation endpoints required by the certificate chain.
-
Identify these endpoints from the CRL Distribution Points and Authority Information Access fields in the relevant certificates, or from the issuing CA's published revocation-service documentation.
-
Enforce the restriction through firewall, secure web gateway, or explicit proxy rules that allow only the required CA hostnames and revocation paths.
-
Allowlist by fully qualified hostname (FQDN), not by IP address.
CA revocation endpoints are frequently served from content delivery networks whose IP addresses change without notice; an IP-based rule will break silently when the CA rotates infrastructure.
General outbound web browsing over port 80 is not required, and no inbound port 80 access to the customer environment is required for this purpose.
Do not disable certificate revocation checking to work around blocked CRL or OCSP access. If a system cannot reach the required CA revocation endpoints, one of two things happens depending on the client's revocation policy:
-
Validation may hard-fail, and the connection is refused;
-
Validation may soft-fail, and the connection proceeds without confirming revocation status, silently weakening the protection the check was meant to provide.
Disabling revocation checking guarantees the second, weaker outcome for every connection.
Review these allowlist entries periodically. CA certificates, intermediate certificates, revocation endpoints, and CA infrastructure can all change over time.
To complete the configuration, you need the following:
-
Access to the Imprivata Admin Console.
-
Access to the Imprivata Hub.
Start the Imprivata Cloud Connect Service
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.
Copy your Enterprise Integration ID
Using the Imprivata Admin Console, copy your enterprise integration ID. You require this value to use the Imprivata Access Managemnt portal 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 Managemnt portal to create the integration token.
Create the Integration Token
Using the Imprivata Hub, 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:
-
Log into the Imprivata Hub.
-
Click the gear icon. Navigate to Integrations.
-
Select Enterprise Access Management 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.
Complete 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 Hub.
Configure Entra ID and sync your users with the Imprivata Cloud Platform
For Entra ID enterprises, additional Entra ID configuration is required to enable Face recognition.
For Active Directory-only enterprises, go to Configure SCIM Integration between EAM and ICP.
After configuring Entra ID and syncing users with the Imprivata Cloud Platform, verify that the users exist in the Imprivata Hub (access.imprivata.com). Complete the following steps.
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 environment is Entra ID only, neither pass-through authentication nor PHS is required.
-
If your Entra ID environment is federated with a third-party IdP, however, PHS is required.
To verify whether 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 Hub (access.imprivata.com).
-
Click the gear icon > Users > Entra ID.
-
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.
After a user has enrolled their face, you can return to this page to remove the enrollment, if necessary. Click the overflow menu next to their name, and then Remove.
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.
You can identify Entra ID configuration issues early, before they affect user authentication, by running a password authentication test:
-
This test can be run for any synced user.
-
If password authentication fails, general guidance on possible causes along with the Entra ID error code are provided.
To run the test:
-
Log into the Imprivata Hub (access.imprivata.com).
-
Click the gear icon > Users > Entra ID.
-
Open the overflow menu in the upper-right corner of the page, and click Test Entra ID configuration.
-
Enter the user credentials of any synced user, and click Test.
SCIM Integration between EAM and ICP
Face authentication with Imprivata's Web authentication user interface is available for Imprivata EAM customers without synchronizing with Entra ID, through SCIM integration between EAM and the Imprivata Cloud Platform (ICP).
About SCIM Integration
SCIM (System for Cross-domain Identity Management) integration allows Imprivata EAM to automatically synchronize user lifecycle events (create, update, enable/disable, delete) with ICP.
With this integration, EAM now communicates with ICP through a standards-based identity API (SCIM v2), and pushes user lifecycle changes directly to ICP. Single-user changes are synchronized immediately; bulk user changes are queued and synchronized hourly.
SCIM or Entra Considerations
-
With the SCIM support, EAM enterprises that are Active Directory-only, and other non-Entra tenants, no longer need to connect Entra ID to their ICP environment to keep their user directories synchronized in ICP.
-
If a customer's ICP is synced with Entra ID, the SCIM integration will not be used.
-
SCIM integration does not support hybrid configurations, where some users are synchronized with Entra ID, and some are Active Directory-only.
-
Enterprises whose users mainly use mobile devices would benefit from a Entra ID integration — SCIM integration does not support "inline" enrollment on mobile devices. Without the Entra ID integration, mobile device users must enroll their face at the Imprivata desktop before they can authenticate with face on their mobile device.
-
This integration is included with Imprivata EAM 26.2 and later. An Imprivata agent upgrade is not required. No additional software, library, or component needs to be installed in your enterprise.
Biometric Consent
In alignment with applicable law, Imprivata's facial recognition service requires users to provide their state or country of residence prior to using face recognition. As applicable by the location of their residence, they agree to one or more of the following:
-
Imprivata-provided biometric data terms and conditions.
-
In addition to the Imprivata-provided terms and conditions, your organization can provide its own notice and legal consent content for biometric use.
After the initial agreement, existing users are required to provide their state or country of residence annually. If required, they must agree to the Imprivata-provided and/or organization-specific terms and conditions for biometric use again to continue using face recognition.
To provide your own notice and/or legal consent content:
-
Log in to the Imprivata Hub (access.imprivata.com).
-
Click the gear icon > Customization > Biometric notice & legal consent.
-
Based on your organization's requirements, upload a biometric consent document and/or a biometric notice document.
-
If you uploaded a biometric consent document, select one or more locations where the consent is legally required.
-
Click Save.
Always consult your legal counsel before adding your own notice and legal consent content for biometric use at your organization.
Face Enrollment
Enroll during Login
-
An unenrolled user clicks Use face at login. EAM attempts to match the face on camera with a user but does not find a match.
-
To match the face on camera with a user, the user is prompted to enter their username.
-
The user is then prompted to continue with inline Face enrollment, or enrollment at the enrollment utility.
Enroll with The Imprivata Agent
-
From the Imprivata agent system tray, go to User Options and click Enroll Authentication Methods.
-
Authenticate with username and password and click Enroll your face to begin the enrollment.
Enroll from Any Device
Users can access My Imprivata Identity from access.imprivata.com on any device.
Access to My Imprivata Identity requires that you configure Imprivata Access Management to use Entra ID as an IdP.
-
The user authenticates to Imprivata Access Management from access.imprivata.com.
-
They click their profile icon in the upper-right corner to open the user menu, and click My Imprivata Identity.
-
From My Imprivata Identity, they click Add an authenticator > Face authentication.
Imprivata Enterprise Access Management can authenticate users who are wearing masks. However, for best results, users should enroll their facial biometric without a mask on.
A user can delete their enrollment from the Imprivata agent in the system tray. Under User Options, they can click Enroll Authentication Methods > Face enrolled > Remove. An Imprivata Enterprise Access Management administrator can also remove the enrollment from the Users page (Users > Users) in the Imprivata Admin Console.
Face Recognition Settings
Opting Out of Face Enrollment
Before a user can use their face for authentication, they are required to complete a biometric agreement workflow. They are asked to provide their residence location, and may optionally be required to consent to certain terms and conditions before enrolling or authenticating with their face.
If the user declines consent, the user’s face is not enrolled and cannot use face authentication. The user will not be automatically prompted to enroll their face again.
The user's workflow continues, using other authentication methods (for example, PIN, password, or proximity card) associated with that workflow.
Enrolling Face Later
If the user wishes to enroll their face at a later date, they may open the EAM enrollment utility, select Face Recognition, complete the biometric agreement flow, and enroll their face.
Users who reside in a location where biometric consent is not required, and choose to not enroll their face, will continue to be prompted to enroll their face each time they attempt to use face authentication.
Prevent Duplicate Face Enrollments
Choose whether to block or allow the same face from being enrolled to multiple user accounts. When blocked, an enrolling user’s face is checked against faces already enrolled, and a duplicate enrollment is prevented.
In the Imprivata Hub, go to the gear icon > Hub security > Face recognition.
Camera Preview During Authentication
The Imprivata Hub provides controls over the onscreen camera preview during Face authentication:
In the Imprivata Hub, go to the gear icon > Hub security > Face recognition. The options are:
-
Hide the camera preview during face authentication
-
Allow users to show the camera preview for troubleshooting
-
Show the camera preview during face authentication
In the Imprivata Hub, go to the gear icon > Customization > Biometric notice & legal consent. On this page you can upload your organization's biometric consent and notice documents, and select the location(s) where consent is legally required.
Store Enrollment Photos
Imprivata administrators can control whether the photo captured during face enrollment is stored when enrollment is completed. This setting allows your enterprise to better support your privacy or data-retention requirements.
The setting applies at the tenant level — it affects all applicable products and workflows for that tenant, not individual users.
This setting does not apply to Imprivata Patient Access.
To access this setting, in the Imprivata Hub, go to the gear icon > Hub security > Face recognition. Store enrollment photos is enabled by default.
-
With the setting off, the enrollment photo is used only to generate the biometric template needed for authentication, and is then immediately discarded.
-
With the setting on, the enrollment photo is used to generate the biometric template needed for authentication, and is then securely stored, subject to Imprivata's data retention policies.
ImprivataEnterprise Access Management supports EPCS with Face recognition with OpenID Connect only.
-
In the Imprivata Admin Console, go to Users > Workflow policy.
-
Go to EPCS workflows > Select desktop authentication methods > Add another method, and add a workflow that includes Face recognition:
-
Face + OTP token
-
Face + Password
-
Face + Imprivata ID
-
-
Click Done.
-
Select another primary factor if needed. For example, if users in this policy must authenticate at endpoints where Face recognition authentication is not available.
Your users may also need an alternate primary factor if they do not consent to Face Recognition. See Biometric Consent.
-
Associate user policies with this workflow, if needed.
-
Click Save.
Face Recognition and Security Lockout
Face Recognition includes the possibility of a user becoming locked out:
-
A user who fails to successfully authenticate 5 times in 5 minutes is blocked: they are prevented from attempting Face Recognition for five minutes. Inactivity timeouts during Face Recognition (15 seconds) count towards the failed attempt count.
-
A user who is blocked three times in a 24-hour period is locked out: they cannot attempt Face Recognition until an Administrator manually unlocks the user.