- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Connecting Robots to Orchestrator
You can connect your robots to Orchestrator in different ways based on the robot authentication settings configured in Orchestrator, typically by an administrator.
The robot authentication settings can be seen and configured on Tenant > Settings, on the Robot security tab, usually by an administrator. Your Orchestrator administrator should provide you with details so as to be able to use the right method to connect your robot.
Sign in with your credentials to connect your robot to Orchestrator. This gives the robot access to Orchestrator resources and provides the user with operational rights to products such as Studio or the Assistant.
- Open the Assistant.
- On the Preferences menu, click Orchestrator settings. The Orchestrator configuration window is displayed.
- On the Connection type field, select Service URL. The content of the window is adjusted according to the selection.
- On the Service URL field, enter the URL of the Orchestrator instance you want to connect to.
- Click Sign In. You are directed to the Login page of your Orchestrator instance.
- Log in as usual.
-
Once your identity is confirmed, the Assistant is populated with the processes in the Orchestrator folders you have access to.
-
When using interactive sign-in, there is no need to create machine objects in Orchestrator.
-
You require the View permission on Packages at the tenant level to download packages and libraries.
Use client credentials to connect attended robots to Orchestrator. The client ID - client secret pair is generated via machine template objects in Orchestrator.
There are two ways to connect your robot with client credentials: using the Assistant or the command line.
Use a machine key to connect attended robots. The machine key is generated in Orchestrator via machine objects.
- 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 accounts.
- Multiple accounts working on the same machine each require a robot created in Orchestrator.
There are two ways to connect your robot with a machine key: using the Assistant or via the command line.
In unattended automation, 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 Interactive Sign-In is enforced, you need to sign in, otherwise you cannot see the processes in the Assistant, and the robot appears as "Connected, Unlicensed".
Use client credentials to connect unattended robots to Orchestrator. The client ID - client secret pair is generated via machine template objects in Orchestrator.
There are two ways to connect your robot with client credentials: using the Assistant or the command line.
Use a machine key connect unattended robots to Orchestrator. The machine key is generated in Orchestrator via machine objects.
- 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.
There are two ways to connect your robot with a machine key: using the Assistant or by using the command line.
To update the default Orchestrator URL service when using the Assistant on a Mac, change it from store.json (/Applications/UiPath Assistant.app/Contents/Robot/uipath.config~/Library/Application Support/UiPath/store.json):
"MAIN_WINDOW_SERVICE_LOGIN_DETAILS": {
"nextServiceUrl": "https://cloud.uipath.com",
"defaultServiceUrl": "https://cloud.uipath.com"
}
"MAIN_WINDOW_SERVICE_LOGIN_DETAILS": {
"nextServiceUrl": "https://cloud.uipath.com",
"defaultServiceUrl": "https://cloud.uipath.com"
}
- What Are My Authentication Settings
- Connecting Attended Robots to Orchestrator
- Interactive Sign-In
- Using the Client Credentials in the Assistant
- Using the Client Credentials in the Command Line
- Using the Machine Key in the Assistant
- Using the Machine Key in the Command Line
- Connecting Unattended Robots to Orchestrator
- Using the Client Credentials in the Assistant
- Using the Client Credentials in the Command Line
- Using the Machine Key in the Assistant
- Using the Machine Key in the Command Line
- Update the Default Orchestrator URL for Mac