orchestrator
2023.4
false
- Getting started
 - Best practices
 - Tenant
- About the Tenant Context
 - Searching for Resources in a Tenant
 - Managing Robots
 - Connecting Robots to Orchestrator
 - Storing Robot Credentials in CyberArk
 - Storing Unattended Robot Passwords in Azure Key Vault (read only)
 - Storing Unattended Robot Credentials in HashiCorp Vault (read only)
 - Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
 - Deleting Disconnected and Unresponsive Unattended Sessions
 - Robot Authentication
 - Robot Authentication With Client Credentials
 - SmartCard Authentication
 
- Audit
 - Settings - Tenant Level
 
 - Resource Catalog Service
 - Folders Context
 - Automations
 - Processes
 - Jobs
 - Triggers
 - Logs
 - Monitoring
 - Queues
 - Assets
 - Storage Buckets
 - Orchestrator testing
 - Other Configurations
 - Integrations
 - Classic Robots
 - Host administration
 - Organization administration
 - Troubleshooting
 

Orchestrator user guide
Last updated Aug 26, 2025
Self-signed certificates are a way to secure your data by encrypting the SAML response when using single-sign on authentication. The following section serves as an example of generating and using self-signed certificates in OKTA.
There are multiple software applications which allow you to generate self-signed certificates, such as OpenSSL, MakeCert, IIS, Pluralsight or SelfSSL. For this example, we use MakeCert. In order to make a self-signed certificate with a private key, run the following commands from the Command Prompt:
makecert -r -pe -n “CN=UiPath” -e 01/01/2019 -sky exchange -sv makecert.pvk makecert.cerC:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\pvk2pfx.exe” -pvk makecert.pvk -spc makecert.cer -pfx makecert.pfx