Breaking Changes
This page lists the breaking changes introduced in Frends 6.3 releases, including changes from earlier versions that are repeated here for visibility. Breaking changes may require action from you before or during an update, such as reconfiguring settings or adjusting running integrations.
Always review the breaking changes for your target version before starting an update. Updating without accounting for breaking changes may affect running integrations and Agent compatibility.
Updating self-hosted Agents with SQL database also requires database schema update through database initializer.
Breaking changes in Version 6.3.2
Log Service on S3 storage
Log retention now uses S3 lifecycle rules by default instead of batch deletion. If your object store does not support lifecycle rules, such as Oracle OCI, turn the lifecycle option off in the Log Service configuration.
Agent log configuration
The per-Process log file of the cross-platform Agent uses a new log category. Only deployments that have customised the Agent logging configuration need to update the category name; see the full release notes.
Role management
The extra checks added in 6.3.1 on which rules an administrator may put into a role have been removed. Managing roles still requires user management administrator rights.
Breaking changes in Version 6.3.1
.NET Runtime version update
On-premise Cross-platform Agents for Frends version 6.3.1 onwards require .NET Runtime 10.0.7 or newer to be installed.
The Windows Agent and Management Web Portal require the .NET 10 hosting bundle to be installed.
Cloud Agents and Compliant Cloud images include .NET 10 out of the box.
Kubernetes StatefulSet Agent groups
The 6.3.1 StatefulSet template adds per-pod persistent volumes (volumeClaimTemplates), which Kubernetes does not allow to be changed in place. A StatefulSet created before 6.3.1 must be deleted with kubectl delete statefulset <name> --cascade=orphan (its pods keep serving) and re-applied. See the README included in the Kubernetes configuration download.
HTTP Triggers and client certificates
The Agent setting EnableClientCertificateValidation is now tri-state. When it is not set (the new default), the Agent requests a client certificate from HTTPS callers only when at least one HTTP Trigger requires certificate authentication. Set it explicitly to true or false to force the previous always-on or always-off behaviour.
Audit log
Failed and denied requests (4xx/5xx) are now audit-logged by default, which increases audit log volume. Set EnableAuditLoggingForFailedRequests to false to keep the previous behaviour.
Database Initializer
the --doNotEnableSnapshotIsolation parameter has been removed. READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION are now always enabled on SQL Server databases.
.NET Runtime version update
On-premise Cross-platform Agents for Frends version 6.3 onwards require .NET Runtime 10.0.5 or newer to be installed.
API Policy migration
We've strived to make the update and migration process as smooth as possible, but due to difference in the configuration model for the new API Policy based authentication and authorization, the following should be noted:
An API Process which has OAuth in the OpenAPI Specification and it's path is included in the API Key rulesets was previously only accessible through OAuth, but now it will be accessible with both authentication methods because it had a matching API Key ruleset. This can be reconfigured by modifying the API Policy
API Policy configuration replaces earlier API Key usage methods where the API Key had to be sent in
Authorization: Apikeyorx-apikeyheaders or in header specified in API Specification, with configurable header for API Keys. As a fallback, these old configurations can also be read if no API Policy configuration exists for the API Key.The update and migration might be blocked if there are inconsistencies between the OpenAPI Specification and Process deployments
Legacy Agent
We strongly recommend updating to the Cross-platform Agent to be able to use the latest technology and solutions possible. Some features will not be supported by it, like the HTTP monitoring which was released in Frends 5.7.
Legacy Agent are being retired. Frends version 6.4 will be the first version to no longer support the Legacy Agent
Frends Platform API changes (for pre 5.7 installations)
The Frends Platform API has been now released and the old v0.9 path has been retired, so you will need to update any calls to the API to target the new v1 path. Also the error result for the API calls has been changed, otherwise the APIs will work the same way as before. Also there are changes to the internal API which is not fully supported for outside use, so if you have used that, you will need to verify everything works separately.
Frends Agent container image path changed
The path for the assemblies inside of the container image is now /app. If there are modifications to the official container image, the new path should be taken into account.
Agents required to have access to the UI
The Agents now fetch their Process and Task packages through the UI, so firewalls on the Agents need to allow outbound access to the Frends UI: <tenant>.frendsapp.com on port 443.
Agent bundled installation LocalDB requires Visual C++ Redistributable (Frends 5.7.3+)
Because the bundled LocalDb for the Legacy Agent was updated, you will need to install Visual C++ 2019 redistributable before installing the bundle. The installer available from here: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170
OpenId Connect (SSO)
Customers using Microsoft Entra ID (formerly Azure AD) as an OpenID login provider for their Frends Tenant must update the App Registration in Azure.
In the Azure portal, go to Manage → Authentication and modify the App Registration's Redirect URI.
Starting with Frends 5.7, the Redirect URI must include an OIDC suffix: signin-oidc-[Application ID].
Example (Frends 5.6 or earlier):
Redirect URI:
https://myfrendstenant.frendsapp.comApplication ID:
3e89b538-f75c-42b5-96f1-402f1ac0a549
Updated Redirect URI for Frends 5.7+:
https://myfrendstenant.frendsapp.com/signin-oidc-3e89b538-f75c-42b5-96f1-402f1ac0a549
Use your own Application ID, obtained from Azure Portal for your Application registration, instead of the example value. The example value will not work for you.
You can add the new URI in advance as an additional URI to the App Registration to ensure functionality before and after the update.
Do not remove or modify the current Redirect URI until Frends is updated to 5.7+, as the new format is incompatible with earlier versions.
No changes are needed in the Frends UI.
Service Bus for Windows (for pre 5.5 installations)
Support for Service Bus for Windows Server is removed, when updating to 5.5+ switching to RabbitMQ for full on-premise deployments is mandatory. This also means that using the Service Bus Trigger no longer works with Service Bus for Windows Server.
Remote Subprocesses (for pre 5.5 installations)
Because of changes to the message busses used by Frends, Agent groups within an Environment should be reinstalled at the same time. This is required when Remote Subprocesses are being used.
Frends.Tasks.Attributes support to be removed
Frends Tasks Attributes was a way of modifying the Parameter editor for Tasks before Frends 4.5.6, when it was deprecated and support for it was removed in 5.5.3. Previously imported Tasks will continue to work normally, but new Task imports will require migration to System.ComponentModel.Annotation to support conditional parameter displays etc.
SQL Server requirements
The minimum supported version of SQL Server is now MS SQL Server 2017 for on-premise deployments.
Last updated
Was this helpful?