Subscribe

UiPath Orchestrator

The UiPath Orchestrator Guide

Connecting Robots to Orchestrator

This article outlines how to choose the Robot to Orchestrator connection method depending on the robot authentication mechanism set in Orchestrator. UiPath provides multiple robot authentication methods, ranging from expiring token authentication to authentication with tokens that never expire.

The three available authentication mechanisms are the resulting state of two Orchestrator tenant settings located on the Settings page > Security tab.

What Are the Types of Robot Authentication?


Standard Authentication

Allow only connections with authentication tokens that never expire by clearing both authentication options on the Settings page > Security tab.

Allow both user authentication and robot key authentication
Enforce user authentication, disable robot key authentication

Implications

Attended

Restrict attended robot authentication in the Assistant to Machine Key. There is no Sign in option displayed in the Assistant, hence users cannot connect Studio and the Assistant to Orchestrator using their credentials.

Unattended

Unattended robots require Machine Key connections at all times.

 

Hybrid Authentication

Allow both standard connections with tokens that don't expire and connections with tokens that expire by enabling Allow both user authentication and robot key authentication and clearing Enforce user authentication, disable robot key authentication.

Allow both user authentication and robot key authentication
Enforce user authentication, disable robot key authentication

Implications

Attended

You can use interactive sign-in to authenticate attended robots. The Sign in option is displayed in the Assistant allowing users to connect Studio and the Assistant to Orchestrator using their credentials, but this is not required.

Unattended

Unattended robots require Machine Key connections at all times.

 

Secure Authentication

Allow only connections with tokens that expire by enabling both authentication options on the Settings page > Security tab. User login is required to make Orchestrator HTTP requests, run attended robots, or view processes in the Assistant.

Allow both user authentication and robot key authentication
Enforce user authentication, disable robot key authentication

Implications

Attended

Restrict attended robot authentication in the Assistant to interactive user sign-in.

Attended robot authentication requires sign-in otherwise the user won't see their associated processes in the Assistant and the robot appears as "Connected, Unlicensed".

Unattended

Unattended robots require Machine Key connections at all times.

Unattended in Attended Mode

For unattended, the host machine is connected and licensed in unattended mode so the designated way to execute processes is Orchestrator.

If you want to use the machine in attended mode (opening the Assistant) when user authentication is enforced, you need to sign in, otherwise you cannot see the processes in the Assistant, and the robot appears as "Connected, Unlicensed".

❗️

Warning!

This authentication method requires recompiling the workflows that use Orchestrator activities or make direct HTTP calls to the Orchestrator API utilizing v2020.10 activity packages or higher.

There is a chance job execution will fail if at least one of below dependencies are used in an automation project:

  • UiPath.System.Activities < 20.10.0
  • UiPath.Persistence.Activities < 1.1.7
  • UiPath.DataService.Activities < 20.10.0
  • UiPath.Testing.Activities < 1.2.0

Use the Project Dependencies Mass Update Tool in Studio to update process dependencies to versions greater than or equal to those provided above. Test before deploying in production.

 

Connecting Attended Robots to Orchestrator


Interactive Sign-In

Use interactive sign-in to authenticate attended robots. The Sign in option is displayed in the Assistant allowing users to connect Studio and the Assistant to Orchestrator using their credentials. Compatible with:

  • Hybrid Authentication
  • Secure Authentication
  1. Open the Assistant.
  2. On the Preferences menu, select Sign In. You are directed to the Login page of your Orchestrator instance.
  3. Log in as usual.
  4. Once your identity is confirmed, the Assistant is populated with the processes in the folders your user has access to. Learn more about interactive authentication.

📘

Note

When using interactive sing-in, there is no need to create Machine objects in Orchestrator.

🚧

Important

Interactive sign-in is not supported in a classic folder context.

 

Machine Key

Use the machine key generated in Orchestrator to authenticate attended robots. Compatible with:

  • Standard Authentication
  • Hybrid Authentication

📘

Note

  • The person handling the Orchestrator configuration in the company should provide the attended users and developers with the correct Orchestrator URL and machine key. Machine objects do not need to be assigned to Orchestrator folders, only users.
  • Multiple users working on the same machine each require a robot created in Orchestrator.

 

Using the Assistant

  1. Open the Assistant.
  2. On the Preferences menu, select Preferences. The Preferences window is displayed.
  1. Navigate to Orchestrator Settings.
  2. In the Orchestrator URL field, enter Orchestrator’s URL and the AccountLogicalName and ServiceName, such as https://cloud.uipath.com/uipathtokyo/uipathkyoto/.
  3. In the Machine Key field, enter the key generated by the machine entity in Orchestrator.
    Learn about the various machine entities in Orchestrator and when to use each.
  4. Click Connect. UiPath Robot is now connected to Orchestrator.

📘

Note:

The High-Density Robots feature only works if the same machine name and key are used when registering each Robot per user.

 

Using the Command Line

  1. Save the machine key generated in Orchestrator to the Clipboard or a file.
  2. Open Command Prompt.
  3. Go to the directory where your UiPath Robot is installed (by default C:\Program Files\UiPath\Studio). For example: cd C:\Program Files\UiPath\Studio.
  4. Use the --connect, -url, and -key command-line arguments in conjunction with the Orchestrator URL and machine key. For example: UiRobot.exe --connect -url https://demo.uipath.com/ -key ba1e4809-2f64-4965-bae2-efda62d20164. UiPath Robot is now connected to Orchestrator. In a High-Density environment, the robot corresponding to each user is connected to Orchestrator.

 

Connecting Unattended Robots to Orchestrator


Machine Key

Use the machine key generated in Orchestrator to authenticate unattended robots. Machine key connections are required at all times for unattended execution. Compatible with:

  • Standard Authentication
  • Hybrid Authentication
  • Secure Authentication

 

Using the Assistant

📘

Note

Administrator privileges are required to perform this procedure for Service Mode Robots.

🚧

Important!

The host machine is connected and licensed in unattended mode so you can execute unattended processes using Orchestrator.

If you want to use the machine in attended mode (opening the Assistant) when user authentication is enforced, you need to sign in, otherwise you cannot see the processes in the Assistant, and the robot appears as "Connected, Unlicensed".

  1. Open the Assistant.
  2. On the Preferences menu, select Preferences. The Preferences window is displayed.
  1. Navigate to Orchestrator Settings.
  2. In the Orchestrator URL field, enter Orchestrator’s URL and the AccountLogicalName and ServiceName, such as https://cloud.uipath.com/uipathtokyo/uipathkyoto/.
  3. In the Machine Key field, enter the key generated by the machine entity in Orchestrator. Learn about the various machine entities in Orchestrator and when to use each.
  4. Click Connect. UiPath Robot is now connected to Orchestrator.

📘

Note:

  • Machine objects need to be assigned to folders in Orchestrator.

  • The High-Density Robots feature only works if the same machine name and key are used when registering each Robot per user.

 

Using the Command Line

  1. Save the machine key generated in Orchestrator to the Clipboard or a file.
  2. Open Command Prompt.
  3. Go to the directory where your UiPath Robot is installed (by default C:\Program Files\UiPath\Studio). For example: cd C:\Program Files\UiPath\Studio.
  4. Use the --connect, -url, and -key command-line arguments in conjunction with the Orchestrator URL and machine key. For example: UiRobot.exe --connect -url https://demo.uipath.com/ -key ba1e4809-2f64-4965-bae2-efda62d20164. UiPath Robot is now connected to Orchestrator. In a High-Density environment, the Robot corresponding to each user is connected to Orchestrator.

 

Updated about a month ago


Connecting Robots to Orchestrator


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.