What’s New in Summer 2026 (11.0)
Monitoring of http requests
Outgoing http requests provide monitoring metrics on request duration and response size.
See also Monitoring with Prometheus.
Tracing
Logging of tracing information for HTTP requests and database queries has been added, and outgoing HTTP requests now include the traceparent request parameter.
See also Tracing.
Defining Cross-Repository Data Sources
Data sources which are independent of a specific repository (cross-repository data sources) can be defined via datasources Configuration.
With cross-repository data sources, the system administration is responsible for both the physical data sources and the Cadenza data sources with all their properties.
In the Management Center, authorized users can view the cross-repository data sources with some of their properties and grant authorizations for them. For cross-repository data sources based on a relational database, authorizations are granted by schema. So a single RDBMS-based cross-repository data source can provide access to multiple schemas; there is no need to create a separate data source for each schema.
For more information see Data Sources.
Configuring
accessmanagerldap Configuration
The LDAP configuration in Cadenza now provides more precise control over user search paths and group mapping rules.
A new LDAP configuration setting, userContextBase, allows defining a dedicated search base for LDAP users.
When configured, user searches are restricted to this subtree, while the existing context-base continues to be used for group searches and technical user login.
In addition, group mapping rules now support a fullDN setting.
It is now possible to configure full LDAP distinguished name instead of context for group mapping rules.
This allows groups to be referenced directly by their full LDAP distinguished name.
The existing context setting remains supported.