2023.10.6
Release date: August 14, 2024
We have enhanced the security measures of the CyberArk credential store in an effort to improve your safety. As a result, lower-level security certificates may now be flagged as invalid.
Plugins.SecureStores.CyberArk.UsePowerShellCLI
parameter to retrieve credentials.
['-', '_', ' ', '.', '#', '(', ')', '@', '$']
. If
you need to allow more characters, you can add them tvia the
Plugins.SecureStores.CyberArk.AdditionalAllowedCharacters
parameter.
Webhooks.VerifyAvailability.Enabled
, to the UiPath.Orchestrator.dll.config
file, with a true
or false
value. Set the parameter to false
to disable webhook reachability validation when configuring the webhook target in the user interface.
We have added the new Allow OS User Authentication option to CyberArk CCP. OS user authentication enhances security by using the credentials of the user logged into the Orchestrator machine.
Plugins.SecureStores.CyberArkCCP.EnableOsUserAuthentication
parameter is set to true
.
Orchestrator now supports server-side encryption with AWS Key Management Service keys (SSE-KMS) for Amazon S3 storage buckets.
- An issue was preventing webhooks for Action Center events from being sent.
- Timeouts occurred when a large number of configured robots retrieved CyberArk® credentials.
- When configuring the CyberArk credential store, the CyberArk Folder field did not support the / or \ separator characters.
- As a result of the My profile page removal, the Orchestrator version was no longer visible in the user interface. You can now find the version at the bottom of the user profile section.
- The Process filter on the Logs page did not include the process names of automations that were run in Studio.
- The Create new menu did not allow keyboard focus on disabled items within the menu list.
- We have fixed an issue that was preventing document validation tasks, specifically those involving the IsEmpty business rule, from being displayed accurately in Action Center.
- The Disable when consecutive job execution fail count and Grace period on disabling the trigger (days) trigger options no longer require the
Features.AutoDisableTriggerAfterConsecutiveJobFailures.Enabled
parameter to be enabled. - HPA scaling of the Orchestrator instance caused intermittent 503 network errors.
- In instances with host level SAML configured, when you accessed Orchestrator through a specific <OrchestratorURL>/<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 Orchestrator.
When you select the Apps tab under Automations, and the Apps service is not enabled, you might get a message that an error occurred, followed by a page reload.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.