Deprecation: ListDiff#elementEqual

In the Java API, method elementEqual of class com.coremedia.translate.workflow.ListDiff has been deprecated. Instead of overriding that method in a subclass, you can instead pass a predicate for equality to a constructor of that class.

(CMS-19502)

Removal: Deprecation for SiteModel's siteIndicatorDepth in Multi-Site

We removed the deprecation notice for siteIndicatorDepth as part of the SiteModel .

As part of this change cm validate-multisite got extended by a new issue code:

The new issue-code is reported at level INFO and is triggered, when using a siteIndicatorDepth different to 0 (zero).

Motivation

As part of CMS-9521 we deprecated siteIndicatorDepth for 2001.1 and changed the default to 0 (zero) rather than 1 (one), as we got aware that many editors struggled with site indicators being hidden in the "depth" of a site – which in the end caused corrupted sites.

Nevertheless, migrating existing content from a depth 1 to depth 0 may raise considerable migration effort, as you have to move all site indicators up one level in one step (while stopping editorial work) and then republish all your sites.

Because of this, we decided to remove the deprecation notice, so that we will support site indicator depths different to 0 also on in the future. The default which ships with CoreMedia Blueprint will stick to the recommended default 0 , though.

(CMS-19378)

cm dump: Dump Text Blobs to Console

cm dump is now able to dump text blob values directly to console. Thus, if your object to dump provides a blob property and it stores some text (or alike) value (such as application/javascript ), you can trigger to write it to console by using:

--blob text

The default remains as is, i.e. blobs are just providing some details on MIME type and size. This is the same as calling cm dump with:

--blob plain

(CMS-18880)

Enhanced Encryption Algorithm For System Passwords

The encryption approach used by cm encryptpasswordproperty has been enhanced, so that you may use a more secure Cipher transformation to encode passwords than the default RSA without padding schema.

To use a better transformation such as RSA/ECB/OAEPWithSHA-256AndMGF1Padding , you may now add it as configuration option to your keystore properties file via CM_CIPHER_TRANSFORMATION , like:

CM_KEYSTORE_PASSWORD=<KEYSTORE_PASSWORD>
CM_KEY_ALIAS=<KEY_ALIAS>
CM_KEY_PASSWORD=<KEY_PASSWORD>
CM_CIPHER_TRANSFORMATION=RSA/ECB/OAEPWithSHA-256AndMGF1Padding

For upgrade scenarios, a fallback exists for decoding passwords from old RSA transformation, so that you may update your passwords one by one.

To re-encode your passwords, use cm encryptpasswordproperty as described in Content Server Manual , section Password Property Encryption once you have set CM_CIPHER_TRANSFORMATION .

(CMS-17851)