I’ve encountered a frustrating issue with XM Directory workflow update triggers. I have a survey which authenticates users via SSO and allows the user to create a unique XM directory entry that can be called back in and updated over time. This has worked fine using LDAP SSO authentication, but all of a sudden it will not recognize the existing records in the XM directory once I switched the authentication to Shibboleth and creates a new record with each new submission, even though it is set to update existing records.

Some important details:

The survey uses an SSO authenticator associated with an XM Directory using Shibboleth to give that user access to the survey, but there is a second authenticator nested in the survey flow that associates with a different XM Directory, and this is the directory I am associating the survey content with. The idea is that an advisor logs into the form, but then they enter a student’s unique identifier to either create a record for them, or to call, edit, end re-log information about that student’s program/progress. So auth1 is the advisor list, auth2 is to associate the survey session with a student on the student XMD so data can be updated for that student and also called back into the survey from the previous session.

I can’t wrap my head around why the authentication method on the first authenticator is causing an issue with duplicate records being created in an XM directory from a Workflow trigger when it works perfectly fine with LDAP as the authentication method for the survey access. I also tried switching the authentication field of the second authenticator to Email from External Data Reference, but the same issue occurs.

Any thoughts, ideas, insights? I would just keep using LDAP, but my institution said they are disabling it soon, so Shibboleth will be my only option if I want to use SSO.