5. 5
AD Integration with On-Prem Orchestrator
Pre-Requisites
LDAP port 389 must be accessible on one or more domain controllers in your domain
Orchestrator server should be in AD domain & can access Active Directory (AD)
Steps
Configure IIS to enable Windows Authentication
Configure the Orchestrator AD Option
Reset IIS
https://docs.uipath.com/orchestrator/docs/configuring-the-active-directory-integration
6. 6
PingOne Integration with On-Prem Orchestrator
Pre-Requisites
Orchestrator server can access PingOne server.
User account should be available in PingOne server with same email address.
Steps
Add a new Application in PingOne
Configure the PingOne Application
Configure the Orchestrator SAML Option
Reset IIS
https://docs.uipath.com/orchestrator/docs/pingone-authentication
7. 7
PingOne Integration with UiPath Cloud Orchestrator
Pre-Requisites
An Automation Cloud organization with an Enterprise or Enterprise Trial license.
Administrator permissions in both Automation Cloud and your third-party identity provider.
User account should be available in PingOne server with same email address.
Steps
Add a new App registration in PingOne
Configure the new App registration
Configure the Orchestrator SAML Option
Reset IIS
https://docs.uipath.com/automation-cloud/docs/configuring-the-saml-integration#b-sample-configuration-for-pingone
8. 8
Azure AD Integration with On-Prem Orchestrator
Pre-Requisites
Orchestrator server can access Azure Active Directory (AD).
Admin permissions in both Automation Cloud and Azure AD.
Steps
Add a new App registration in Azure AD
Configure the new App registration
Configure the Orchestrator Azure AD Option
Reset IIS
https://docs.uipath.com/orchestrator/docs/configuring-sso-azure-ad
9. 9
Azure AD Integration with UiPath Cloud Orchestrator
Pre-Requisites
Automation Cloud organization with an Enterprise Trial or Enterprise license.
Admin permissions in both Automation Cloud and Azure AD.
Organization administrator needs an Azure AD account that uses the same email address as the
Automation Cloud local account.
Steps
Add a new App registration in Azure AD
Configure the new App registration
Configure the Orchestrator Azure AD Option
https://docs.uipath.com/automation-cloud/docs/azure-ad-integration
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
Orchestrator has 3 different services bundled in the standalone installation i.e. Orchestrator, Identity and WebHook.
Orchestrator: It is the core component which manages Robots, Processes, Queues etc.
Identity: this service is responsible to manage all the authentication and integration with Authentication Providers like SAML, Google etc.
WebHook: Webhook manages all the notification to other application.
