2023.4.2
Release date: 10 August 2023
.xaml
sources (i.e. the Include Sources option selected in the Publish options > Compilation settings section) can now be viewed in their entirety in the package explorer. This applies to Windows and cross-platform projects.
-
Important: The fix only applies to this version. For previous versions, you need to add the following section to the web.config file:
We have fixed an issue that prevented Swagger authentication if Orchestrator and Identity Server were deployed as Azure app services with different URLs.
<rewrite> <outboundRules> <rule name="CSP"> <match serverVariable="RESPONSE_Content-Security-Policy" pattern=".*" /> <action type="Rewrite" value="default-src 'self' https://<YOURIDENTITYURL>;connect-src 'self' https://<YOURIDENTITYURL>;script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline';img-src 'self' data:;font-src 'self'" /> </rule> </outboundRules> </rewrite>
<rewrite> <outboundRules> <rule name="CSP"> <match serverVariable="RESPONSE_Content-Security-Policy" pattern=".*" /> <action type="Rewrite" value="default-src 'self' https://<YOURIDENTITYURL>;connect-src 'self' https://<YOURIDENTITYURL>;script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline';img-src 'self' data:;font-src 'self'" /> </rule> </outboundRules> </rewrite>
-
When you deleted a user from the host tenant, then created another user with the same username and e-mail address as the one that you had deleted, you could no longer log in to the any non-host tenant. This occurred due to a missing rule around provisioning a new user once another user with the same information was deleted. This issue is now fixed.
-
The
minLevel
NLog setting in the Identity Serverappsettings.json
file was not being honored. The defaultminLevel
is "Info" indicating that logs of "Info" severity and above should have been logged. However, theminLevel
was not being considered, and logs with lower severity levels, specifically "Trace" and "Debug", were also being written to the logs. -
An intermittent issue was affecting robots. During these faults, an "Invalid request!" error message would appear, and various assets were failing.
-
This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
You can download the latest product version from the Customer Portal.
Added on 6 November 2023
In versions 2023.4.0 through 2023.4.2, if you have an Active Directory (AD) integrated environment, you will see sporadic failures from the product leading to the IIS application pool restarting. This issue has been fixed in version 2023.4.3, but it still affects the aforementioned versions. As such, if you use AD, we highly recommend that you directly install or upgrade to 2023.4.3. Otherwise, you will encounter functionality issues.