We are trying to correlate the Google Workspace accounts with the attribute Externalids due to it stores the employee in the organization with the following format:
{“value”:“99882”,“type”:“organization”}
In order to achieve the correlation we created a custom attribute in the identity profile called Google externalids that contains the exactly the same value.
{“value”:“99882”,“type”:“organization”}
The problem is that the accounts are not correlating and both attributes are strings so they should match, Any ideas?
Trying checking your correlation configuration, your “Google externalids” identity attribute should be mapped with “Externalids” account attribute.
Then try running unoptimized account aggregation that should correlated your accounts to identities.
However previous the account aggregation, we already had configured the account correlation indicating that the identity attribute “Google externalids” must be equal to account attribute “Externalids” but is failing the correlation.
@JaimeIvanHuertaMontes Have you validated if this custom identity attribute on your identity profile is mapped to the right source and attribute and it is actually populated for all the identities in your system? Can you run a full identity search report and compare it against the google workspace source accounts and see if identity attribute vs account attribute value matches?
Also, do you mind showing a snippet of your account schema and correlation config?
Thanks team,
we could resolved the case it was the transformation rule, It had the wrong transformation on SailPoint, the value for in Google for externalids is:
[{“value”:“222”,“type”:“organization”}]
However on the user interface SailPoint shows it as follows in the account section of the connector :
{“value”:“222”,“type”:“organization”}
That confused us however when we downloaded the accounts csv files in SailPoint it shows the value as in google
[{“value”:“222”,“type”:“organization”}]
So we changed the transform rule adding the chacter “[” and “]”, problem solved.
wrong rule: {“value”:“222”,“type”:“organization”}
correct: [{“value”:“222”,“type”:“organization”}]
