Additional Configurations

Updating Credentials

If you need to change and/or update your credentials, the procedure below details the steps that must be performed on your Orchestrator and Insights machines.

Orchestrator Database Credentials

On Your Orchestrator Machine

1. Open the UiPath.Orchestrator.dll.config file.
2. In the connectionStrings section, modify the connectionString parameter of the key name="Default" as follows:
3. For SQL Authentication: connectionString="Data Source={YOUR_ORCH_DB_HOST};Initial Catalog={YOUR_ORCH_DB_NAME};User ID={YOUR_ORCH_DB_SQL_USER};Password={YOUR_ORCH_DB_SQL_PASSWORD}" />
4. For Windows Authentication: connectionString="Data Source={YOUR_ORCH_DB_HOST};Initial Catalog={YOUR_ORCH_DB_DATABASE_NAME};Integrated Security=true" />

Example for SQL Authentication:

<add name="Default" providerName="System.Data.SqlClient" connectionString="Data Source=sql.uipath.com;Initial Catalog=UiPathOrchestrator;User ID=docs-uipath;Password=SecretP@ssword" />

Example for Windows Authentication:

<add name="Default" providerName="System.Data.SqlClient" connectionString="Data Source=sql.uipath.com;Initial Catalog=UiPathOrchestrator;Integrated Security=true" />

On Your Insights Machine

Running The Insights Installer in Repair mode

To update SQL credentials on the Insights machine the installation must be modified. This can be done by selecting "Modify" for UiPath Insights Installer in Window's Apps and Features page or running the installer exe from an admin cmd as UiPathInsightsInstaller.exe /modify.

You will be required to provided the Insights Portal Address and the Insights Admin email and password to proceed.

On the page titled update Orchestrator Database Configuration new data base credentials can be added. To save the changes click "Next" and then "Change" on the final page.

Insights Database Credentials

On Your Orchestrator Machine:

1. Open the UiPath.Orchestrator.dll.config file.
2. In the connectionStrings section, modify the connectionString parameter of the key name="Insights" as follows:
3. For SQL Authentication: connectionString="Data Source={YOUR_INSIGHTS_DB_HOST};Initial Catalog={YOUR_INSIGHTS_DB_NAME};User ID={YOUR_INSIGHTS_DB_SQL_USER};Password={YOUR_INSIGHTS_DB_SQL_PASSWORD}" />
4. For Windows Authentication: connectionString="Data Source={YOUR_INSIGHTS_DB_HOST};Initial Catalog={YOUR_INSIGHTS_DB_NAME};Integrated Security=true" />

Example for SQL Authentication:

<add name="Insights" providerName="System.Data.SqlClient" connectionString="Data Source=sql.uipath.com;Initial Catalog=UiPathInsights;User ID=docs-uipath;Password=SecretP@ssword" />

Example for Windows Authentication:

<add name="Insights" providerName="System.Data.SqlClient" connectionString="Data Source=sql.uipath.com;Initial Catalog=UiPathInsights;Integrated Security=true" />

On Your Insights Machine:

Running The Insights Installer in Repair mode

To update SQL credentials on the Insights machine the installation must be modified. This can be done by selecting "Modify" for UiPath Insights Installer in Window's Apps and Features page or running the installer exe from an admin CMD as UiPathInsightsInstaller.exe /modify.

You will be required to provided the Insights Portal Address and the Insights Admin email and password to proceed.

On the page titled update Insights Database Configuration new data base credentials can be added. To save the changes click "Next" and then "Change" on the final page.

Updating the Insights Certificate

Note: Before updating the Insights certificate, ensure that this new certificate is trusted inline with relevant policies for your company.

If you are using an expired or incorrect certificate, and you need to change it, you should be aware that Insights has its own mechanism put in place for this purpose.

To change a certificate, take the following steps on the Insights Server:

1. Make sure the following requirements are met:
   • The new certificate must support the original Insights hostname.
   • A .pfx file should be available for the certificate.
   • Modern browsers require that a certificate have a SAN attribute that maps to the certificate subject name.
2. Generate the .pfx file with the help of your network admin. We do not recommend using a self-signed certificate, but if you nonetheless decide to do so, please see Creating a Self-Signed SAN SSL Certificate.
3. Import the newly generated .pfx file into the Personal store. If the certificate was generated via MMC, it should already be there.
   • Follow the indications provided in Importing the SAN Self-Signed Certificate to Other Machines.
   • In the previous step, instead of importing the certificate to Trusted Root, import it to the Personal Node.
   • Additionally, you need to enter the password for the .pfx to import the certificate.
4. Right-click the certificate, select Open, go to the Details section, and then choose Copy To File.
   • When asked if the private keys should be exported, select No.
   • When asked for the file type, select Base-64 encoded X.509 (.CER).
5. If the .pfx file was generated via MMC, redo the previous step, but export the private keys. The format will be pre-set.
6. Once the .cer file and the .pfx file have been generated, go to http://localhost:3030.
7. On the webpage, in the Update Certificate section, select Browse.
8. Select the .pfx file and enter the password. When done, click Upload.
9. After the upload is complete, you need to add the SSL certificate. Start by opening the .cer file that you have previously created in Notepad.
10. Copy the contents exactly, paste them into the SSL Certificate section, and select Save.
11. Double-click the .cer file and import it into Trusted Root. Insights needs the Public Certificate to be in Trusted Root.
12. Access https://InsightsURL. If it loads, then everything is complete.

Using Firefox

It is not initially possible to access Insights via your Firefox browser when using a self-signed certificate. This is a known issue due to Firefox blocking HTTPS sites from using self-signed certificates unless explicitly allowed by the user.

To avoid this issue, prior to accessing Insights for the first time and without being logged into your Orchestrator account, follow these steps:

1. Navigate your browser directly to the Insights Portal using the format https://<Your_Insights_Host>/app/account. For example, https://insights-test:8081/app/account.
2. When prompted by Firefox, explicitly select to continue on to the site.
3. You are then redirected to the Orchestrator login page. Login using your Orchestrator credentials and you can now access the Insights page and Portal.

Using Edge and Internet Explorer With Self-signed Certificates

If you are planning on using non-Chromium Edge (version < 79) or IE browsers to access Insights, you must first:

1. Export a copy of your self-signed certificate from your Insights server.
2. Copy the certificate to the machine(s) where you are using Edge or IE.
3. Install the certificate into the Trusted Root Certification Authorities.

Configuring Insights to Be Case Insensitive

If you are not using unique case-insensitive names for all custom variables in your workflows (i.e. successfulTransaction and SuccessfulTransaction), the Insights connector will fail. Insights cannot distinguish between two variables with the same name, even with different capitalization. You can remedy this by setting the Insights connector to be case insensitive. To do so:

1. On the Insights machine, navigate to C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\UiFrost\uipath_insights.properties.
2. Find the property called insights.case.sensitive, and set it to false.
3. Restart the Sisense.JVMConnectorsContainer service.
   Note: Setting Insights to case insensitive will cause duplicate columns to be merged into a single column.