Hey, I’ve posted this in compass as well since I think it fits there better but haven’t had much luck yet.
I’ve set up a correlation config for a Google Workspace (G Suite) connector but it doesn’t seem to have any effect. I’ve compared the two values (in the source, in accounts that are already correlated and the corresponding identity attribute) and they’re identical.
The attribute I’m correlating against is “externalIds” from Google Workspace, which is imported and stored in this format: {"value":"<emp_id>","type":"organization"}. I’ve made a transform that is applied in the identity profile to generate an identity attribute with the same value. The same identity attribute is also used in the Create Account provisioning policy and it works just fine.
Technically this attribute could be a list but we’re not using other types of externalIds and this account attribute is always in this format.
Nevertheless, the correlation config does not seem to have any effect and IDN always falls back to the default built-in displayName correlation instead.
I’ve reset the source and ran multiple unoptimised aggregations with no luck.
Are there any limitations in using non account ID/displayName account attributes in the correlation config? Or any other reason why this could be failing?
I don’t think the externalIds object from G Suite will work for manager correlation natively. You will probably need to pull in that object into a custom account attribute, then in the Identity Profile, transform it so that it is a string which contains only the emp_id, and use that new value as the account attribute used for manager correlation.
If that doesn’t work, I would recommend you open a Support ticket, and they will be able to assist you with specifics.
Thanks for the reply - this is actually in regards to account correlation, not correlating managers.
The idea is that accounts in G Suite should correlate to identities based on employee ID.
I think the issue here is that externalIds is an array and while it’s displayed as a string via UI, is actually stored as an array (due to the fact that jsonpath output will always be an array if input is an array), hence it’s never equal to the identity attribute.
