Deprecation of Generic Analytics Connectors

The integration of Analytics Connectors based on Elastic Core is deprecated, i.e. extension es-alx and parts of extension alx, including the analytics doctypes. Functionality for website tracking will still be available.

Deprecated features:

These features are discontinued and will be replaced by an integrated solution.

(CMS-28158)

Configurable Cache Duration for Outdated Transformed Blobs

Added a new configuration property delivery.outdated-transformed-blob-cache-duration to control how long outdated or yet unknown transformed blobs are to be cached in a multi-CAE scenario (cae.single-node=false). Before this fix, CAE send a cache-control header with max-age of 0 seconds. This value is now configurable. Consider that a yet unknown cache should not be cached for long because the CDN should ideally cache the correct transformed blob for a given URL. The cases to cover are that (1) either a more up-to-date CAE generated the link and the CAE answering the request for the transformed blob does not yet know about the updated blob and (2) a client has stored a very old version of a transformed blob URL for which the blob data is no longer cached by the CDN. A CAE cannot distinguish between these two cases but serves the currently (either outdated or newer) known transformed blob. The new configuration property allows projects to optimize for scenario (1) or (2) by setting a (1) short duration or (2) a long duration.

Configuration example:

# Set cache duration to 1 hour
delivery.outdated-transformed-blob-cache-duration=1h

Upgrade Information

(CMS-28032)

JUnit Jupiter: Updated to 5.13.2

JUnit Jupiter has been updated to 5.13.2. Note, that this release introduces deprecations, for example, for ArgumentsProvider so that you should implement another signature of provideArguments.

For details, see the corresponding release notes: JUnit 5 Release Notes.

(CMS-28006)

Third-Party Update: commons-io 2.19.0

Apache Commons IO has been updated to 2.19.0.

(CMS-27839)

LdapUserProvider Connection Improvements

LDAP roundtrips ere executed with a timeout now, in order to avoid blocked threads in case of certain problems. The timeout (ldap.timeout) as well as the maximum number of connections (ldap.max-connections) is configurable now. However, the default values are supposed to be suitable for most projects, and there should be no need to change them unless concrete problems occur. There is another new configuration property ldap.referral-throw-handling to control the details of referral handling. It is still experimental, because the details concerning referrals depend on the particular setup of the LDAP servers, and this has not yet been tested exhaustively. But if you encounter problems with the default behaviour, you should give it a try.

See com.coremedia.ldap.LdapUserProviderConfigurationProperties for details.

(CMS-23359)