- Getting Started
- Requirements
- Best Practices
- Installation
- Updating
- Migrating Elasticsearch Indices
- Changing the Orchestrator / Identity Server URL
- Updating Using the Windows Installer
- Updating Using the Azure Script
- Identity Server
- Troubleshooting startup errors
Changing the Orchestrator / Identity Server URL
If you decide to manually upgrade your Orchestrator / Identity Server instances from single node to multi-node, you may need to change the Orchestrator / Identity Server URL. The case where you should change the Orchestrator / Identity Server URL is when the load balancer URL is used in a multi-node installation, as it is independent from any node name.
If the single-node installation is configured to be used by a load balancer, upgrading to a multi-node installation does not require changing the public URL.
Several steps are required when changing the Orchestrator or Identity Server public address, in order to maintain Orchestrator fully functional. This page describes these steps.
REPLACE function.
-- Declare variables for the current server name and the new server name
DECLARE @CurrentServerName NVARCHAR(255) = 'server1'; -- Input: e.g., 'server1'
DECLARE @NewServerName NVARCHAR(255) = 'server2'; -- Input: e.g., 'server2'
-- Update statement using REPLACE function
UPDATE identity.ClientRedirectUris
SET RedirectUri = REPLACE(RedirectUri, @CurrentServerName, @NewServerName)
WHERE RedirectUri LIKE '%' + @CurrentServerName + '%'; -- Update only if the row contains 'server1'
UPDATE identity.ClientPostLogoutRedirectUris SET RedirectUri = REPLACE(PostLogoutRedirectUri, @CurrentServerName, @NewServerName)
WHERE PostLogoutRedirectUri LIKE '%' + @CurrentServerName + '%'; -- Update only if the row contains 'server1'-- Declare variables for the current server name and the new server name
DECLARE @CurrentServerName NVARCHAR(255) = 'server1'; -- Input: e.g., 'server1'
DECLARE @NewServerName NVARCHAR(255) = 'server2'; -- Input: e.g., 'server2'
-- Update statement using REPLACE function
UPDATE identity.ClientRedirectUris
SET RedirectUri = REPLACE(RedirectUri, @CurrentServerName, @NewServerName)
WHERE RedirectUri LIKE '%' + @CurrentServerName + '%'; -- Update only if the row contains 'server1'
UPDATE identity.ClientPostLogoutRedirectUris SET RedirectUri = REPLACE(PostLogoutRedirectUri, @CurrentServerName, @NewServerName)
WHERE PostLogoutRedirectUri LIKE '%' + @CurrentServerName + '%'; -- Update only if the row contains 'server1'-
Update the
OrchestratorUrlparameter within Identity Server's appsettings.Production.json file with the new public address of Orchestrator. -
Update the
ExternalAuth.System.OpenIdConnect.RedirectUriparameter within Orchestrator's UiPath.Orchestrator.dll.config (formerlyweb.config) with the new valuehttps://[NewOrchestratorAddress]/signinsystemopenidconnect. -
Update the
ExternalAuth.System.OpenIdConnect.PostLogoutRedirectUriparameters within Orchestrator's UiPath.Orchestrator.dll.config (formerlyweb.config) with the new valuehttps://[NewOrchestratorAddress]/.
-
Replace
[OldOrchestratorAddress]and[NewOrchestratorAddress]with your actual Orchestrator URL addresses. -
Make sure the certificates you use have the appropriate permissions set to prevent an internal server error. Refer to Troubleshooting Certificates for more details.
-
The Platform Configuration Tool provides as an alternative way to change the Orchestrator URL.
