Face Recognition Authentication
Enabling Face recognition authentication requires that you:
-
Configure a connection to the Imprivata Cloud Platform.
-
Configure an identity provider (IdP) to authenticate users to the Imprivata Access Management portal.
-
Configure Entra ID and sync your users with the Imprivata Cloud Platform.
-
Configure a user policy to enable Face recognition.
Download the Imprivata Facial Biometric Consent and Enrollment User Guide.
Requirements
-
Face recognition authentication requires an Authentication Management license and a Remote Access license.
-
Users in a policy enabled for facial biometric 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 by synced from AD to Entra ID with Entra Connect or maintained in Entra ID only.
-
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.
-
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.
-
Face recognition is supported on the Imprivata agent Type 1, Type 2, and Type 3, installed on a Citrix server. Face recognition is not supported via VDA.
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.
You can use either of the following methods to configure the connection.
Before you begin:
-
Determine if a connection to the Imprivata Cloud Platform has already been configured by logging into the Imprivata Admin Console. The status of the connection is available in the Status panel on the right-hand side. A green check mark for Access Management integration indicates a connection has been configured.
-
If you need to configure the connection, contact Imprivata Services. Imprivata Services will create an Imprivata Cloud Platform 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 setup to configure the connection.
Complete the following steps to use the Imprivata Access Management setup to configure the connection. To complete the configuration, you need the following:
-
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).
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.
Add the following hosts to your firewall allowlist:
-
<tenantID>.sys.imprivata.com
-
astra.sys.imprivata.com
-
access.imprivata.com
-
metadata.app.imprivata.com
-
file-access.app.imprivata.com
-
idp.app.imprivata.com
For non-US regions, replace the .com with the appropriate domain suffix for your region, for example, *.sys.imprivata.eu.
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 Cloud Tenant Setup wizard 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 Cloud Tenant Setup wizard to create the integration token.
For more information on starting the Imprivata Cloud Connect service, see Stop and Restart This Connection.
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.
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 Access Management portal.
If you have previously configured an identity provider (IdP) for access to the Imprivata Access Management portal (access.imprivata.com), you can create an integration token from the Imprivata Access Management portal instead of having to use the Imprivata Cloud Platform Tenant setup. To complete the configuration, you need the following:
-
Access to the Imprivata Admin Console.
-
Access to the Imprivata Access Management portal.
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 Access Management portal, 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 Access Management portal.
-
Click the gear icon. Navigate to Integrations.
-
Under Enterprise Access Management integration, 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 Access Management portal.
Configure an IdP to authenticate users to the Imprivata Access Management Portal
Configuring an IdP is required to authenticate administrators to the Imprivata Access Management portal. You need access to the Imprivata Access Management portal to synchronize your Entra ID users with the Imprivata Cloud Platform.
If you have already configured access to the Imprivata Access Management Console, 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 Access Management portal 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. For more information, see Enroll Facial Biometrics.
-
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 Access Management portal.
-
Skip to the You're ready to go screen, and click the link to log in to the Imprivata Access Management portal.
You can configure Entra ID as an IdP to authenticate users to the Imprivata Access Management portal. 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 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 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 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.
The following are generic steps to configure any external third-party IdP to authenticate users to the Imprivata Access Management portal. 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 Entra ID and sync your users with the Imprivata Cloud Platform
Additional Entra ID configuration is required to enable Face recognition. 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 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.
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.
Configure a User Policy
-
In the Imprivata Admin Console, go to Users > User policies page , and select a user policy.
-
On a user policy page, go to the Authentication tab > Desktop Access authentication section.
-
Select Face recognition as a primary factor.
-
Select a second factor for Face recognition:
-
Security Key
-
Imprivata PIN
-
Password
-
Proximity Card
-
Device-bound passkey
-
Imprivata PIN or Device-bound passkey
-
Device-bound passkey or Password
-
Security Key or Imprivata PIN or Proximity Card or Device-bound passkey
BEST PRACTICE:For enhanced protection against sophisticated attacks, pair Face Authentication with a strong second factor like device-bound passkey or proximity card.
-
-
Select another primary factor if needed. For example, if users in this policy must authenticate at endpoints where Face recognition authentication is not available.
-
Click Save.
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 their face as an authenticator. 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.
Always consult your legal counsel before adding your own notice and legal consent content for biometric use at your organization.
To provide your own notice and/or legal consent content:
-
Log in to the Imprivata Access Management console (access.imprivata.com).
-
Click the gear icon > Customize.
-
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.
Face Enrollment
-
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.
Configure a User Policy
-
In the Imprivata Admin Console, go to Users > User policies page, and select a user policy.
-
On a user policy page, go to the Authentication tab > Desktop Access authentication section.
-
Select Face recognition as a primary factor.
-
Select a second factor for Face recognition:
-
Security Key
-
Imprivata PIN
-
Password
-
Proximity Card
-
Device-bound passkey
-
Imprivata PIN or Device-bound passkey
-
Device-bound passkey or Password
-
Security Key or Imprivata PIN or Proximity Card or Device-bound passkey
BEST PRACTICE:For enhanced protection against sophisticated attacks, pair Face Authentication with a strong second factor like device-bound passkey or proximity card.
-
-
Select another primary factor if needed. For example, if users in this policy must authenticate at endpoints where Face recognition authentication is not available.
-
ClickSave.
Desktop Authentication with Face Recognition as a Primary Factor
-
At the Imprivata Enterprise Access Management login screen, the user selects Use facial bio. The name of the user currently selected for authentication is displayed on screen. If this is not the intended account, the user can change it by editing the username in the username/password hexagon before proceeding.
-
The camera turns on, and the user is prompted to center their face in the frame and look at the camera.
-
When the user's face biometric is successfully captured, the user is logged into the desktop.
If their User Policy is configured with a second factor required for Desktop Authentication, the user completes that factor before the user is logged in.
Desktop Authentication with Face Recognition as a Secondary Factor
-
At the Imprivata Enterprise Access Management login screen, the user selects the available primary factor (Security Key, Password, or Proximity Card).
-
The user successfully authenticates with their primary factor.
-
The camera turns on, and the user is prompted to center their face in the frame and look at the camera.
-
When the user's facial biometric is successfully captured, the user is logged into the desktop.
-
In the Imprivata Admin Console, go to Users > Workflow policy.
-
Go to Web SSO workflows > Select authentication methods > Add another method, and add a workflow that includes Face recognition:
-
Face + OTP token
-
Face + Imprivata ID
-
Face + SMS Code
-
Face + Email
-
-
Click Done.
-
Optional — Select an interval to allow users to skip the second factor on saved devices. The maximum allowed is 120 days.
-
Click Save.
-
In the Imprivata Admin Console, go to Users > Workflow policy.
-
Go to Remote Access workflows > Select authentication methods > Add another method, and add a workflow that includes Face recognition:
-
Face + OTP token
-
Face + Imprivata ID
-
Face + SMS Code
-
Face + Email
-
-
Click Done.
-
Optional — Select an interval to allow users to skip the second factor on saved devices. The maximum allowed is 120 days.
-
Click Save.
Imprivata Enterprise 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.
-
Click Save.
Stop and Restart an Imprivata Cloud Platform Connection
You can stop and restart this connection for the whole enterprise from any Imprivata Appliance Console, or on an appliance-by-appliance basis. The two statuses for the connection are Running or Disabled (stopped).
-
In the Imprivata Appliance Console, go to System > Operations > Imprivata Cloud Connect.
-
Imprivata Cloud Connect status is either Running or Disabled (stopped).
-
Select Stop/restart options.
-
Select from:
-
Stop Imprivata Cloud Connect on this appliance
-
Restart Imprivata Cloud Connect on this appliance
-
Stop Imprivata Cloud Connect on all appliances
-
Restart Imprivata Cloud Connect on all appliances
NOTE:In this context, "Restart" means "start this stopped connection" and also "restart this connection that is already running".
-
-
Click Go.