These instructions only apply if you have a standalone installation of Orchestrator. If you are using Orchestrator in Automation Suite, follow the Automation Suite instructions instead.

📘

Note

After enabling this integration, local user accounts are linked to an Active Directory user and, in the process, their username attribute is updated to the format user@domain. Thus the user can no longer use their original username to sign in and must instead use the new username in the format user@domain, or the email address tied to the Active Directory account.

🚧

Prerequisites

1. To integrate with Windows Active Directory (AD) and use Windows Authentication, LDAP port 389 must be accessible on one or more domain controllers in your domain.

2. Work with your IT administrators to ensure the Orchestrator server can access your Active Directory (AD).

3. If you plan on using LDAP over SSL (LDAPS), you must obtain and install certificates for configuring secure LDAP on each domain controller. For more information and instructions, see the article LDAP over SSL (LDAPS) Certificate.

About integration options

When users log in to Orchestrator with their Active Directory credentials, Orchestrator uses the Kerberos protocol to authenticate users.

Step 1. Configure the Orchestrator cluster

Requirements for multi-node clusters

• The nodes in the cluster must be deployed under a load balancer. Use the load balancer host name whenever the hostname is required in these instructions.
• The Orchestrator application pool must be configured to run under a custom identity. The custom identity should be a domain account.

Setting a custom identity

This is only required if you are running a multi-node cluster, or a single-node cluster with a load balancer.
For single-node clusters with no load balancer, this is optional.

1. Open IIS (Internet Information Services Manager).
2. In IIS, in the Connections panel on the left, click Application Pools.
3. Go to Identity > Advanced Settings > Process Model > Identity.
4. In the Application Pool Identity dialog, select Custom account and specify a domain-qualified user account.
5. Click OK to apply your changes.
6. Close IIS.

SPN setup

If the Orchestrator application pool is configured to run under a custom identity, that account must have an SPN registered for the host name.
This step is required if you are running:

• a multi-node cluster because you must define a custom identity or
• a single-node cluster with a load balancer, which is treated the same as a multi-node cluster.

This step is not required if:

• you are running a single-node cluster with no load balancer and
• you chose to use a custom identity, but you used the cluster computer name as the custom identity

On a domain-joined machine that has write access in the target Orchestrator organization and tenant:

1. Open the Command Prompt.
2. Change the directory to C:\Windows\System32, by using the cd C:\Windows\System32 command.
3. Run the command setspn.exe -a HTTP/<hostname> <domain account>, where:
   • HTTP/ - The URL at which your Orchestrator instance can be accessed.
   • <domain account> - The name or domain\name of the custom identity as which the Orchestrator application pool is running.

Step 2. Configure IIS to enable Windows Authentication

If you have a multi-node installation, you must perform IIS configuration on each of your cluster nodes.

1. Open IIS (Internet Information Services Manager).
2. In the Connections section, under the Sites node, select UiPath Orchestrator.
3. In the main panel, double-click Authentication to view the details.
4. Select Windows Authentication and then, in the Actions panel on the right, select Advanced Settings.
   If not already enabled, enable Windows Authentication to continue with these instructions.

5. Click the UiPath Orchestrator site on the left, and then double-click Configuration Editor in the main area.

6. In the Configuration Editor, along the top, from the Section list, select system.webServer/security/authentication/windowsAuthentication.
7. For useAppPoolCredentials, set the value to True:

Step 3. Configure Orchestrator

1. Log in to the Management portal as a system administrator.
2. Go to Users and select the Authentication Settings tab.
3. In the External Providers section, click Configure under Active Directory:

The Configure Active Directory panel opens at the right of the screen.

4. Select the Enabled checkbox.
5. If you want to only allow users to log in using their Active Directory credentials, select the Force automatic login using this provider checkbox.
   If selected, users can no longer log in using their Orchestrator username and password; they must use their Active Directory credentials, with a domain-qualified username.
6. Optionally edit the value in the Display Name field to customize the label for the Windows authentication button that is displayed on the Login page.
7. Restart the IIS site. This is required whenever you make changes to External Providers.

Step 4. Verify the authentication protocol

Now that the integration is configured, we recommend performing a test login using AD credentials and verifying that the Kerberos protocol is used for logging in.

1. Log in to Orchestrator using your Active Directory credentials to create a login event.
   Note the time when you logged in.
2. Open Event Viewer in Windows.
3. Go to Window Logs > Security.
4. In the list of security events, look for the entry with the following specifics:
   • Event ID: 4624
   • Date and Time: Today's date and the time when you logged in with your Active Directory credentials.
5. Double-click the row to open the event properties dialog.
6. On the General tab, scroll down to the Detailed Authentication Information section and check the following:

If Kerberos authentication was used:

• the value of Authentication Package must be Negotiate
• the value of Package Name must be blank (-) because this only applies for NTLM. If this value is NTLM V2, then the default authentication protocol was used and not Kerberos.

In Google Chrome incognito mode, the browser prompts for credentials and it does an explicit authentication with credentials. The flow does work and it uses Kerberos.