2023.10.5

Release date: August 14, 2024

AWS Signature Version 4 support

Automation Suite now uses AWS Signature Version 4 for all S3 API requests. This impacts the use of Automation Suite with S3 servers that do not support AWS Signature Version 4.

Bug fixes

• Running a health check would create temporary network policies that were not cleaned up when the check concluded. We have fixed the issue.

• For AI Center and Task Mining, the ListBucket API prerequisite check failed when using an external objectstore. However, AI Center and Task Mining do not use the ListBucket API permission. We have removed the unnecessary check.

• In instances with host level SAML configured, when you accessed Automation Suite through a specific <Automation_Suite_URL>/<Organization_name> URL and selected the host level SAML login option, the ACS URL was incorrectly generated using the organization ID from the URL, instead of the expected host level ACS URL. We have fixed this. The system now correctly generates the host-level ACS URL during a host level SAML login, irrespective of the specific organization URL used to access Automation Suite.

• Previously, you could not save your SMTP settings without providing a username and password, even though these details were optional. This behavior no longer occurs.

Known issues

Test Automation SQL connection string is ignored

Erratum - added October 17, 2024: When you provide an SQL connection string under the orchestrator.testautomation section of the input.json file, the uipathctl binary ignores the connection string and uses the one under the orchestrator section instead. To address the problem, see the Troubleshooting section.

Health check fails for component that is no longer used

Running a health check on AKS results in an [ARGOCD_REDIS_PODS] failure for ArgoCD Redis HA. However, ArgoCD Redis HA is no longer used in Automation Suite on AKS. We fixed the issue in Automation Suite 2023.10.6.

Pods cannot communicate with FQDN in a proxy environment

Erratum - added October 17, 2024: In a proxy environment, if the proxy server uses the same port as the TCP port of any other service in the Istio service mesh, such as port 8080, pods cannot communicate with the FQDN. The issue causes the following error:

System.Net.Http.HttpRequestException: The proxy tunnel request to proxy 'http://<proxyFQDN>:8080/' failed with status code '404'.

To fix the issue, see Automation Suite on EKS/AKS troubleshooting.

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.

Bundling details

Product versions

To find out what has changed on each Automation Suite product, visit the following links.

If the product is greyed out, this new Automation Suite version does not bring any changes to it.

DISCOVER	BUILD	MANAGE	ENGAGE
Automation Hub 2023.10.5	Automation Ops 2023.10.5	AI Center 2023.10.5	Action Center 2023.10.5
Task Mining 2023.10.5	AI Computer Vision 2023.10.4	Insights 2023.10.5	Apps 2023.10.5
Process Mining 2023.10.5	Document Understanding 2023.10.5	Orchestrator 2023.10.6
		Test Manager 2023.10.5
		Data Service 2023.10.5

Internal third-party component versions

For the Kubernetes versions that each Automation Suite version supports, see Kubernetes compatibility.

This Automation Suite release bundles the following internal components:

Component	Version
Istio	1.22.2
ArgoCD	2.10.9
Prometheus	2.53.0
Grafana	11.1.0
Fluentd & Fluent-bit	logging-operator: 4.8.0 logging-operator-logging: 4.8.0
Gatekeeper	3.16.3
Cert-Manager	1.14.5
Velero	6.2.0

Migration tool version

The migration tool version you need depends on the standalone products you plan to migrate and the targeted Automation Suite version. For more details, see Migration compatibility matrix.

For instructions on migrating a standalone product to the current version of Automation Suite, see Full migration.