Installing and Configuring Support for Omnissa Horizon Cloud
This topic includes information about configuring Enterprise Access Management so that the Imprivata agent can sign users to virtual desktops and applications delivered by Omnissa Horizon Cloud.
Before You Begin
Before you configure the integration, make sure your environment meets the following requirements:
-
Active Omnissa Horizon Cloud environment with support for Published Desktops and Published Applications workflows. Your Omnissa Horizon Cloud administrator account must be able to change Identity and Access and Client Settings.
-
Imprivata Enterprise Access Management (EAM) version 26.3, server and agent must both be version 26.3. Earlier versions and mixed versions are not supported.
-
The Imprivata agent installed on the endpoints, and on the virtual desktops where single sign-on inside the session is required.
-
Omnissa Horizon Client version 2609 or later installed on the endpoints. Earlier versions and legacy VMware Horizon Client do not support this authentication method.
-
The Secondary Identity Provider feature enabled for your Omnissa Horizon Cloud organization. This feature is not available to all customers by default. If it is not visible in your console, ask Omnissa to enable it.
-
Omnissa Horizon Cloud TrueSSO configured, if you want users to be signed in to Windows automatically.
-
An Imprivata Admin Console account with permission to create application profiles and edit the Virtual Desktops settings.
You will create some values in one console and enter them in another. Use the following table to keep track of them.
| Value | Where you get it | Where you use it |
|---|---|---|
| Redirect URI | Fixed value: http://127.0.0.1:9096/callback | OIDC application profile; Horizon Cloud secondary identity provider |
| Metadata URL | Imprivata Admin Console, OIDC application profile |
Imprivata Admin Console, Virtual Desktops |
| Tenant ID (five characters) | Part of the Metadata URL | Horizon Cloud secondary identity provider |
| Client ID | Imprivata Admin Console, OIDC application profile | Horizon Cloud secondary identity provider; Imprivata Admin Console, virtual desktop |
| Client secret | Imprivata Admin Console, OIDC application profile | Horizon Cloud secondary identity provider only |
| Company domain | you choose it when you add the secondary identity provider | Imprivata Admin Console, virtual desktops |
| Client Access address | Horizon Cloud console, Branding | Imprivata Admin Console, virtual desktops |
Installation Sequence
The application profile defines how Omnissa Horizon Cloud is allowed to request identity information from Imprivata.
-
Sign in to the Imprivata Admin Console.
-
Go to Applications > Single sign-on application profiles. From the Add App Profile dropdown, select Application using OpenID Connect.
-
Enter a name for Application profile name and Application user-friendly name
-
Under Redirect URIs, enter the following address:
http://127.0.0.1:9096/callbackIMPORTANT:
The Imprivata agent receives the sign-in response on the local computer, so the address must be the loopback address 127.0.0.1 on port 9096, using http and not https. If this value does not match exactly, sign-in fails. -
Under Claims, confirm the following claims are selected:
Scope Claim name Attribute ID Token Access Token Profile name User logon name - Pre WK (sAMAaccountName) Selected Not selected Profile given_name First name (givenName) Selected Not selected Profile family_name Last name (surname) Selected Not selected Profile upn user logon (userPrincipalName) Selected Selected Email email Email address (mail) Selected Not selected IMPORTANT:
On Profile scope, the upn claim must be selected for both ID Token and Access Token. Omnissa Horizon Cloud uses the UPN in the access token to identify the user. If Access Token is not selected for UPN, users cannot sign in. -
Under Client credentials, click Generate client credentials. The Client ID and Client secret are generated, copy both and store the secret securely.
NOTE:
The client secret is shown only once. The next time you open the profile the field shows only a Generate new client secret link. Generating a new secret means you must enter the new value in the secondary identity provider. -
Leave Public client clear.
-
Click Save.
-
Click View and copy Imprivata (IdP) OpenID Connect metadata. Copy and store the Metadata URL and Imprivata Tenant ID, the five-character value in the address. It has the following form
https://oidc.idp.cloud.imprivata.com/<TenantID>/.well-known/openid-configuration -
At the end of this step you should have recorded the Metadata URL, Tenant ID, Client ID, and Client Secret.
Omnissa Horizon Cloud must be told to trust Imprivata as a source of user authentication.
-
Sign in to Omnissa Cloud Services and open Horizon Cloud.
-
Go to Integrations > Identity & Access > Manage > Identity Provider.
-
Under Secondary Identity Provider Details, click Add.
-
In the Add Secondary Identity Provider dialog, enter the following:
-
Secondary Identity Provider: Imprivata
-
Company domain: Enter a company name, for example mycompany. You will enter this same name in the Imprivata Admin Console to configure TrueSSO.
-
Broker URL: Displayed by Horizon Cloud for reference. It is generated from the Company domain.
-
Redirect URL:
http://127.0.0.1:9096/callback.NOTE:
The Redirect URL must be identical to the Redirect URI you entered in the OIDC application profile. -
Tenant ID: The five-character tenant ID from OIDC Application Profile Metadata URL.
-
Client ID: The Client ID from OIDC Application Profile.
-
Client Secret: The client secret from OIDC Application Profile.
-
-
Click Add
IMPORTANT:
The Secondary Identity Provider feature is not available to all Omnissa customers by default. If you do not see Secondary Identity Provider Details on the Identity Provider tab, contact Omnissa to enable the Secondary Identity Provider feature for your organization before you continue.
The Imprivata Agent connects to Horizon Cloud through your organization’s custom client access subdomain.
-
In the Horizon Cloud console, go to Settings > Client Settings > Manage > Branding.
-
Note the Custom client access subdomain. It has the following form:
https://mycompany.omnissahorizon.comYou will enter this address in the Imprivata Admin Console in the next step.
Enter the connection and OIDC application profile details in the Imprivata Admin Console.
-
In the Imprivata Admin Console, go to Computer > Workspace Access.
-
Locate the Omnissa section, then select Omnissa Horizon - Desktops.
-
In the Connection Manager field, enter the client access address from Find your client access address step, for example:
https://mycompany.omnissahorizon.com. -
Leave Use SAML authentication clear.
-
Under Horizon Cloud, enter the following:
-
Metadata URL: The OIDC Application Profile Metadata URL
-
Client ID: The Client ID from OIDC Application Profile.
-
Company domain: The Company domain you chose in OIDC Application Profile.
-
If your Horizon Cloud environment uses TrueSSO to sign users in to Windows automatically, you must also configure Imprivata to work with TrueSSO. Follow the steps on Configuring Support for Omnissa True SSO.
Verify the Configuration
Verify that users can launch a Horizon Cloud desktop or application without entering their credentials again.
-
Sign in to an endpoint with the Imprivata Agent, for example by tapping a badge.
-
Launch a Horizon Cloud desktop or application from the Imprivata Agent.
-
Confirm that the desktop or application opens without prompting for credentials.
If sign-in does not work, see the Troubleshooting section.
Troubleshooting
Probable cause: One or more of Metadata URL, Client ID, or Company domain is blank in the Imprivata Admin Console, or the Connection Manager address does not match.
Resolution: Verify that all three values are entered for the matching Connection Manager, in both the Desktops and Apps sections if both are used.
Probable cause: Redirect URI mismatch, incorrect client secret, or upn is not selected for Access Token
Resolution: Confirm the Redirect URI is http://127.0.0.1:9096/callback in both consoles, regenerate and re-enter the client secret, and confirm upn is selected for both ID Token and Access Token.
Probable cause: Horizon Cloud still has the previous secret
Resolution: Update the client secret in the secondary identity provider in Horizon Cloud
Possible cause: The endpoint cannot resolve the client access address.
Resolution: Confirm the endpoint can resolve and reach your omnissahorizon.com address
Possible cause: TrueSSO is not configured or not working.
Resolution: Review Configuring Support for Omnissa True SSO.