Skip to main content
Welcome to the Semarchy Community
Welcome to the Semarchy Community

Join now to ask questions and share information with your peers.

Alexis liked 4 days ago

Security Notice - Log4J2 CVE-2021-44228

A vulnerability has been reported under the CVE-2021-44228 reference, affecting the Log4J2 (Log4J version 2) library, commonly used in applications for logging services.

To summarize:

  • CVE-2021-44228 impacts Log4J2 (Log4J version 2), which is not used in Semarchy xDM.
    xDM instances use Log4J1 (Log4J version 1) which is not vulnerable to CVE-2021-44228 attacks as described in the CVE.
  • Log4J1 (one) has other reported vulnerabilities which can be easily identified and mitigated.
  • Upgrading the Log4J1 library used in xDM is a "technical debt" tracked as MDM-10824. We have in our plans to perform that upgrade as part of our next minor release... (More)
Mony liked 11 hours ago
Peter TseSemarchy Team
Training & Solutions Architect at Semarchy

Hi Mony

You will need to modify the default Master ID Survivorship Rule  2with the appropriate Consolidation Strategy that will enable the required SourceID to be preferred.

Regards, Peter

Mony liked 18 hours ago
David JonesSemarchy Team
Technical Client Success Manager at Semarchy

Consider the following scenario, where a user attempts to modify the Member ID attribute of a Golden Record

Unable to Edit Member ID
Unable to Edit Member ID

The Date of Birth attribute can be edited, however, Member ID cannot. In this instance, editing can be enabled by making a change to Survivorship Rules > Override Rule configuration.  

Survivorship Rule > Override Rule
Survivorship Rule > Override Rule

 In Application Builder, navigate to the Entity > Survivorship Rules. Here, we change the Override Rule from No Override to Override – until next user changes. Save the changes in Application Builder, then use the Refresh applicaton option in the application to propagate changes.  

Editing is now enabled for Member ID
Editing is now enabled for Member ID
Robin liked a day ago
Fathia JamaSemarchy Team
Sr. Customer Success Consultant at Semarchy

How to Correctly Configure Postgres Search Path

When installing Semarchy on a PostgreSQL database, customers sometimes run into errors like this:

+- ERROR: function uuid_generate_v1() does not exist Hint: No function matches the given name and argument types. You might need to add explicit type casts.

This error can occur when the search path in the database is not correctly configured.

Do you have a search_path problem?

The above error will be thrown if:

  • The function does not exist.
  • The function exists, but you do not have access to it.
  • The function exists, and you have access, but it is not in the search_path.
/* First confirm... (More)