xDM

We have released today on semarchy.com this patch for Semarchy xDM 5.3.

You can read the release notes (5.3.23) for the list of issues.

Breaking Changes

• MDM-14408: To increase security, the X-Forwarded-For, Forwarded, and X-Real-IP HTTP headers are now ignored by default. A new -DallowXForwardedHeaders system property is available to process these headers, which should be activated only when the xDM instance is exclusively accessible through a reverse proxy.

Bug Fixes

• MDM-14407: Third party module upgrade: Apache Tomcat (xDM Preconfigured).
• MDM-14405: Starting xDM on a Mac M1 or M2 CPU using an arm64 JDK fails with a org.osgi.framework.BundleException: Could not resolve module error.
• MDM-14355: With ID-matched entities, the absence of publisher ID for referenced records causes components such as browsing, named queries, enrichers, and validations to fetch incorrect references when several master records have the same ID but different publishers. A new -Dmdm.dataaccess.resolveIDMatchedRefsWithSamePubId system property allows bypassing this limitation by forcing the publisher ID to the same value as the child record’s. This property is set to false by default and must be set to true to enable this behaviour.
• MDM-14164: File upload security enhancement. The maximum number of files that can be uploaded at once in Configuration and in the Application Builder is now set to 100 files. A new -Dcom.semarchy.mdm.maxImportFileCount system property allows customizing this value.
• MDM-14138: When a form is opened in a stepper, a nested exception com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'order' is raised with SQL Server under certain conditions.
• MDM-13876: HTTP connections are not closed by REST data notifications.

The offer on Docker will be updated to this version in the following days.