There has been a change in the account name and account ID value from the non-auth source itself. When we aggregate, two source accounts are created for the same user in the same source.(one with the old account name and one with the new account name).
What steps should we take when a non-auth source changes the accountname and accountID value?
Hi @Manju22,
Are you using this dynamic changing attribute in the correlation logic?
Correlation logic should be using unique values so that the accounts get correlated correctly to the identity.
If the account is correctly correlated, then ISC will not provision or create another account for the same source.
Thanks
@Manju22 The best practice is to pick the unique attribute as Account ID from your target source which will never get change.
If for some reason it changed or I would say duplicate accounts are created then it’s a data issue, you should not entertain this kind.
If it is a data issue it should be fixed in target only.
Also you can look into correlation logic find some attribute which make these two account distinctive and possibly correlate with Identity.
Email addresses are the only thing that correlates. Due to org changes, the account name and account ID from the target source have been changed only once and will not change again.
I already set up the source with the old account name and account ID. Now, when I aggregate, it creates duplicate accounts with both old and new account names. What are some ways we can prevent certain situations? Would it be okay to remove all accounts and run aggregation?
@Manju22 If it is a web service connector, then you can use beforeOperation / afterOperation rule to filter (meaning write some condition to get only accounts which are required).
I am not sure about kind of data you have, probably you can find some difference or can ask your app team to add some custom attribute which will make the difference between these duplicate accounts.
And then in your rule have a check to bring only those account which you want to aggregate (if the account contains that attribute as yes or no or anything you decide to put)
@Manju22 ,
Are you using email address as the correlation logic and account name for this source?
What is the authoritative source for the email address identity attribute?
Also could you please let us know what connector you are using here?
Thanks
I would recommend resetting the accounts on this source, then aggregating again.
POST {{baseUrl}}/beta/sources/:id/remove-accounts
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.