- 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
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Reconfiguring authentication after upgrade
If you are upgrading Orchestrator to this version and you've previously enabled any external identity provider authentication, there are a series of manual configurations to be performed at the external identity provider level.
Previously created users are propagated to the UiPath Identity Server database.
UiPath® Identity Server acts as a federation gateway for a series of external identity providers (Google, Windows, Azure AD, and SAML2). You can configure their settings from the Management portal, under Users > Authentication Settings, in the External Providers section.
Upon upgrading to this version of Orchestrator, any external identity provider authentication enabled in Orchestrator is automatically migrated to Identity Server, along with all the existing users. However, some manual changes are required after the upgrade.
If you upgraded Orchestrator from version 2020.4 (or from a later version) to the current version, skip this section.
If you upgraded from a version prior to 2020.4:
- In the external provider's settings, modify the Return URL by adding
/identity
at the end of your Orchestrator URL so that you havehttps://OrchestratorURL/identity
. - Save the changes to the external provider.
- Restart the IIS site for the changes to apply.
Continue with the instructions on this page for additional configuration that is required actions for the external identity providers you use with Orchestrator.
If you've previously configured Google to recognize a new Orchestrator instance , then you need to perform these steps:
If you've previously enabled Windows authentication, no further actions are required.
If you've previously configured Azure AD to recognize a new Orchestrator instance, then you need to perform these steps:
ADFS
If you've previously configured ADFS to recognize a new Orchestrator instance, then you need to perform these steps after upgrading Orchestrator:
If you've previously configured Google to recognize a new Orchestrator instance, then you need to perform these steps:
Okta
If you've previously configured Okta to recognize a new Orchestrator instance, then you need to perform these steps: