Smooth migration from legacy to current hash generating strategy.

Since the existing DefaultSecureHashCodeGeneratorStrategy used for securing blob transformation was considered vulnerable to possible DoS attacks, a new default MD5SecureHashCodeGeneratorStrategy was introduced with version 10.2007.

The new MD5SecureHashCodeGeneratorStrategy wont match hashes created by the former DefaultSecureHashCodeGeneratorStrategy . Cached URLs would cause a HTTP 403 (forbidden) status code. Therefore CoreMedia now provides a smooth migration path by using a strategy which will accept hashes created by both, the DefaultSecureHashCodeGeneratorStrategy and the MD5SecureHashCodeGeneratorStrategy . New hashes will be created using the new MD5SecureHashCodeGeneratorStrategy .

The migration mode may be enabled by setting cae.hashing.migration-mode=true .

(CMS-18868)

Runlevel based health indicator added to the Spring-Boot health actuator

A runlevel based health indicator has been added to all repository clients. The indicator will be available at :8081/actuator/health/uapiconnectionreadiness . The indicator will be set to:

Because the indicator will be DOWN if the connection will be unavailable because of a runlevel change with a grace period, this endpoint can be used in a Kubernetes environment as a readiness probe to make sure a repository client such as the CAE or the Headless-Server will be removed from the Service endpoints and won't receive traffic.

With this change the existing :8081/actuator/health/repositoryhealth check has been renamed to :8081/actuator/health/uapiconnectionhealth .

(CMS-18579)