Configuring the certificates

This page explains what certificate configuration entails at the time of installation.

The installation process generates self-signed certificates on your behalf. These certificates are FIPS-compliant and will expire in 90 days. You must replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes. If you do not update the certificates, the installation will stop working after 90 days.

If you installed Automation Suite on a FIPS-enabled host and want to update the certificates, make sure they are FIPS-compliant. For a list of eligible ciphers supported by RHEL, see RHEL documentation.

Aside from the above certificates, you may need to provide additional trusted CA certificates if you want the cluster to trust external services. Example: SQL Server CA Certificate, SMTP Server CA Certificate, etc.

Updating cluster certificates

The installation bundle provides a cluster management tool that enables you to update certificates post-installation.

To access it, navigate to the location of the installer bundle:

cd /opt/UiPathAutomationSuite/

For instructions on updating the certificates, see Managing certificates.

Accessing a cluster that uses self-signed certificates

If you are using a self-signed certificate, take the following steps to access the cluster:

You need to add CA (Certificate Authority) Bundle certificate to the trust store for the following:

• Client machine
  • Machine on which robot will run.
  • Machine on which you will access Automation Suite from the browser.
• First server machine (requirement for air-gapped)
  • Machine on which air-gapped bundle will be downloaded and extracted.

Use the following command to add the certificate to the trust store of the RHEL machine.

sudo cp --remove-destination rootCA.crt /etc/pki/ca-trust/source/anchors/
sudo update-ca-trust