xDM 2023.1.3 is available!


We have released today on semarchy.com this patch for Semarchy xDM 2023.1 (LTS).

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

Breaking Changes

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

Bug Fixes

  • MDM-12395: Leading and trailing spaces are removed from attribute values in browsing forms and collections.
  • MDM-14114: Reference fields do not show the selected record after selection when using a reference picker.
  • MDM-14209: The Always Authored in the MDM Override Strategy defined for an attribute does not allow editing its value on authoring forms.
  • MDM-14235: Form fields in sections with vertical layout use the entire vertical space available instead of being top-aligned.
  • MDM-14236: API keys security enhancement.
  • MDM-14268: Default user settings defined in the configuration of the internal identity provider are not taken into account when creating a new user.
  • MDM-14361: Starting a workflow instance from the browsing form of a record having a UUID primary key fails with an unexpected server error.

The offers on Docker and Azure (Solution Template) will be updated to this version in the following days.

1 person likes this



Can you please tell where to put the new allowXForwardedHeaders property ?

For example, in the setenv.sh file, should we have something like that ?

CATALINA_OPTS="$CATALINA_OPTS -DallowXForwardedHeaders=true"

All the other properties seem prefixed with keys like "xdm.etc".

Best regards,


Hi Alexis,

That's correct, you should put the property in CATALINA_OPTS just like you indicated. The naming of properties depends on how and where they apply.

1 person likes this
Login to post a comment