Configuring Support for Omnissa True SSO
Configuring support for True SSO requires that you enable Imprivata Enterprise Access Management for Kerberos authentication.
Omnissa True SSO Support Introduced
As part of True SSO authentication, the Microsoft Certificate Authority (CA) creates a certificate on behalf of the user. True SSO uses this certificate to log the user into their virtual desktops or applications, without requiring them to enter their Active Directory credentials.
Enabling Kerberos support allows Enterprise Access Management to trust the True SSO user certificate, which extends the True SSO environment to Imprivata Secure Workspace Access (formerly Imprivata Virtual Desktop Access) functionality.
For additional details on the True SSO workflow, see Introducing True SSO in Omnissa Horizon 7.
When True SSO support is enabled:
-
The user logs into Omnissa Workspace ONE.
-
The user opens the virtual desktop or applications manually.
-
The Imprivata agent is active and is available to:
-
Provide Imprivata Secure Workspace Access functionality.
-
Proxy user credentials to Imprivata SSO-enabled applications, if licensed for Imprivata Single Sign-On.
-
Before You Begin
Before you begin:
- Verify that the True SSO environment is functioning normally, independent of Enterprise Access Management, before installing and configuring Imprivata components. For more information on configuring True SSO, see "Setting up True SSO" in the Omnissa Horizon documentation.
- Review Imprivata Enterprise Access Management for SSO Supported Components to confirm that your True SSO environment meets all of the minimum or recommended requirements.
Imprivata Secure Workspace Access supports True SSO on Windows endpoints only.
Kerberos Prerequisites
Review the following prerequisites before you begin:
-
The Imprivata keytab utility, which you use to create and upload a keytab file to an appliance, uses ktpass. The keytab utility is installed with the Imprivata agent.
-
Ktpass is part of the Microsoft Windows Server resource kit. The resource kit tools are installed as part of the server role installation.
-
The endpoint computer from which you run the keytab utility and the primary appliance to which the Imprivata agent communicates must be in the same Active Directory domain.
For example, if the fully qualified domain name (FQDN) of the endpoint computer is endpoint.example.com, then the Imprivata appliance FQDN could be server_name.example.com.
-
The Service Principal Name (SPN) of the appliance that the keytab utility registers with Active Directory is case-sensitive. The hostname and the domain name that appear in the Imprivata Appliance Console of this appliance must contain all lowercase letters.
-
If the Imprivata enterprise includes more than one domain that share a trust relationship, for example a parent company (company.com) and two subdomains (us.company.com and eu.company.com), make sure that at least one appliance is placed in company.com. Upload the keytab file to this appliance.
Uploading to the appliance that is in the second-level domain (SLD) ensures that the keytab file is valid for all domains.
Enabling Kerberos Authentication
Enabling Kerberos authentication requires that you:
Configuring Kerberos authentication requires access to the following:
- Domain administrator access to an endpoint computer on which the Imprivata agent is installed.
- The Imprivata Appliance Console.
- The Imprivata Admin Console.
If more than one person is responsible for domain administration, appliance administration, and Enterprise Access Management administration, coordinate with these individuals before beginning.
Configuring Network Protocol Time (NTP) servers makes sure that the Kerberos ticket does not expire before the appliance can extract the user identity from the Kerberos ticket.
Complete the following for each appliance in the enterprise to enable time synchronization.
-
In the Imprivata Appliance Console, go to Network > NTP.
-
Enter the IP address for one or more NTP servers.
-
Click Save.
The endpoint computer from which you run the keytab utility and the primary appliance to which the Imprivata agent communicates must be in the same Active Directory domain.
For example, if the fully qualified domain name (FQDN) of the endpoint computer is endpoint.example.com, then the Imprivata appliance FQDN could be server_name.example.com.
- Log into the endpoint computer.
- Open the registry editor and go to the ISXAgent registry key:
HKLM\SOFTWARE\SSOProvider\ISXAgent
- Use the IPTXPrimServer value to confirm that the agent's primary appliance is in the same Active Directory domain as the endpoint computer.
Creating and uploading a keytab file establishes a Kerberos trust relationship between Enterprise Access Management and Microsoft Active Directory. You use the Imprivata key tab utility, which is installed with the Imprivata agent, to create and upload a keytab file. After the keytab file is uploaded to the appliance, it is propagated to all other appliances in the enterprise.
NOTE: Obtain the administrator user credentials of the appliance to which you are uploading the keytab file. The Imprivata keytab utility requires these credentials to upload the keytab file.
-
As a domain administrator, log into an endpoint computer to which the Imprivata agent is installed and open a command prompt.
-
At the command prompt, type the following and press Enter:
cd \Program Files (x86)\Imprivata\OneSign Agent\x64 -
Type ISXKerbUtil and press Enter. The utility returns the names of the following:
-
The domain.
-
The domain controller.
-
The appliance host name in the Service Principal Name (SPN) format.
-
-
Using the User Principal Name (UPN) format, type the username of the domain account that has Super Administrator rights in the Admin Console and press Enter.
Example: username@example.com
-
Enter the password of the domain account, with the Super Administrator rights you provided above, and press Enter.
-
Enter a password that meets the Active Directory complexity requirements and press Enter. The utility does the following:
-
Creates a domain user account named ssoKerberos.
-
Sets the password.
-
Creates and uploads the keytab file to the appliance.
NOTE: If the Imprivata keytab utility detects that a domain user account is already mapped to the SPN, it updates the domain account with the password you entered. If the utility detects that multiple domain user accounts are mapped to the SPN, the utility detects which user it previously created and updates it with the password you entered; the remaining users are removed from the SPN.
-
The Imprivata keytab utility creates the keytab file with all of the supported cryptographic types supported by Windows Server.
NOTE: Only 1 keytab file is allowed per Imprivata enterprise.
- In the Imprivata Admin Console, go to the Users menu > Directories page.
- Click the name of the domain from which you created the keytab file.
- Go to Kerberos authentication and click 5 keytab files.
- Verify that the Windows Server keys are using the following cryptographic types:
- DES cbc mode with CRC-32
- DES cbc mode with RSA-MD5
- ArcFour with HMAC/md5
- AES-256 CTS mode with 96-bit SHA-1 HMAC
- AES-128 CTS mode with 96-bit SHA-1 HMAC
Identify the computers to which Kerberos authentication applies and configure a computer policy. Configuring the computer policy enables the computers in the policy for Kerberos authentication.
Step 6a: Create a Computer Policy for VMs
- In the Imprivata Admin Console go to the Computers menu > Computer policies page.
You can select an existing computer policy from the list, or make a copy of the Default Computer Policy as a starting point. If you want to edit an existing computer policy, click the existing computer policy name, and skip to Step 6b: Configure the Computer Policy for VMs.
-
To copy the Default Computer Policy, select Default Computer Policy , then click Copy.
-
Click Default Computer Policy (2).
-
Rename the computer policy.
Step 6b: Configure the Computer Policy for VMs
-
Click the General tab, go to the Authentication section, and select Accept Kerberos authentication in place of SSO authentication.
-
In the Desktop experience section, select Override log in and locking of the Windows workstation, then select Use Windows credential provider.
-
Click Save.
Step 6c: Assign the Computer Policy to VMs
To manually assign the computer policy:
-
Go to the Computers menu > Computers page.
-
Select the computers to which you want to apply the computer policy.
-
Select Change policy
-
Select Choose a policy and the name of the policy configured for Kerberos authentication.
-
Click Change Policy.
Use computer policy assignment rules to assign a computer policy to existing endpoint computers and to automatically assign the policy to endpoint computers added in the future.
-
Go to the Computers menu > Computer policy assignment page.
-
Click Add new rule.
-
Enter a Name for the assignment rule.
-
Select one of the following:
-
Computer IP address, and then enter the range of IP addresses to include in the computer policy.
-
Computer host name to match the computer policy to a specific computer.
-
Imprivata agent type to apply the computer policy to all computers with a specific Imprivata agent.
Install the Imprivata Agent to the Virtual Machines
The Imprivata agent must be installed on each virtual machine from which Imprivata Secure Workspace Access functionality is required.
The installation can be pushed to groups of computers or installed on one computer at a time, depending on your organization's preferences. See
Create and Assign Computer Policy for the Virtual Machines
Create and assign a computer policy for the virtual machines. The computer policy must be enabled for Kerberos authentication.
- In the Imprivata Admin Console, go to the Computers menu > Computer policies page.
- You can select an existing computer policy from the list, or make a copy of the Default Computer Policy as a starting point. If you want to edit an existing computer policy, click the existing computer policy name, and configure the computer policy.
- To copy the Default Computer Policy, select Default Computer Policy , then click Copy.
- Click Default Computer Policy (2).
- Rename the computer policy in the Name field.
- Go to the General tab > Authentication section.
- Select Accept Kerberos authentication in place of SSO authentication.
- Click Save.
Computer policy assignment rules let you assign a policy to existing virtual machines and make sure that the policy is automatically assigned to virtual machines that are added later.
To use a rule to assign the computer policy:
- Go to the Computers menu > Computer policy assignment page.
- Click Add new rule.
- Name the rule and select the assignment criteria.
- Select the policy you created and click Save.
Verify that the Imprivata Agent is Enabled for Kerberos
You can use the Imprivata agent logging utility (ISXTrace) to verify the Imprivata agent is functioning normally in the True SSO environment.
-
Use a test user to log into Workspace ONE and launch a desktop or application.
-
From the virtual machine that is hosting the virtual desktop or application, verify that the Imprivata agent icon is in active status.
-
Ctrl + click the icon, and click Trace Utility.
-
Click Logging options (hammer icon) to open the ISXTrace Options dialog.
-
Select Log to Viewer (Real-Time Logging), and click OK.
-
Verify that the log includes messages that Kerberos is employed.
-
Re–open the ISXTrace Options dialog, select No Log, and click OK.
-
Close the tracing utility.