I’m working with Authoritative Source Migration and followed the steps as per the Community Document. The issue I’m noticing is with the net new identities, which got created from the new Authz identity profile and aren’t there in the legacy HR sources, that their IdentityNow accounts which is an internal account for ISC is appearing with name as invalid. The identities which just migrated from legacy to new didn’t have this issue, it’s just there for the new identities created from new identity profile. Any ideas on the root cause and solution?
It is basically an Account Name of your new Auth source’s account schema. Check whether it is showing as invalid to all identities or a set of identities from new auth source, and verify the data if it is only for few identities.
Account name is correctly populated in identity attribute which is also getting derived from New Auth source. It’s showing invalid only for net new identities incoming from new Auth source which were not there in legacy HR Source.
Seems like the legacy HR source’s identities are just switching the identity profile and it is as expected and that’s the reason you are not seeing the issue in existing identities.
For the new HR source, I assume the below could happen
These identities created via non authoritative source in the backend for holding the uncorrelated account and it will not be visible on UI until you get an account from auth source for those identities.
If both the sources have not marked the same account attribute as “Account Name”, the identity attribute account name will not be from the auth source. These are expected behaviors.
