Any Identity created in Sailpoint from an application which is not marked as source application, those identities are flagged as uncorrelated Identities.
you can stop these identities to be created in Sailpoint by checking Option “Only create links if they can be correlated to an existing identity.” option on aggregation Task.
If I understand correctly you mean “An application which is not marked as source application” is that the application is selected as “Authoritative Application”?? if this true no, is not check
About the next “you can stop these identities to be created in Sailpoint by checking Option “Only create links if they can be correlated to an existing identity.” option on aggregation Task.”
Why should I stop creating those identities in sailpoint, currently the option is unchecked. should I check it???
Its a normal behavior that the application chat has all the identities uncorrelated??
This option will correlate the application accounts with identities, if there is an identity which satisfies the correlation configuration given in the application config. If you do not want account from this application to be created as an identity you can check this option. Also, every correlated identity needs to be connected to one authoritative source.
Hi @aishwaryagoswami thank you for you answer.
So because the chat application is not an authoritative application thus all those identities are not correlated, because ONLY the correlate identities are the ones which are check on the application as authoritative application, is that correct?
Application → check as authoritative application -->identities get correlated with sailpoint, where how? i want to understand what this identities get correlate to what
Application → not check authoritative application → identities dont get correlated
if i check the spt_identity, are the identities correlated and not correlated
Quoting a little bit of the solution here " Identities who only have accounts in a non-authoritative sources are often called “orphans”. In case of an orphaned account for a natural person, it could be a left-over (some account that has not been removed, while it should have been), or the correlation logic simply did not suffice to automatically find a match. In the latter case, such an account needs to be correlated manually. Legal “orphans” could be service accounts, system accounts and other technical accounts.
Orphaned accounts can still correlate to existing identities without becoming marked as “correlated”".
I would recommend, go through the entire thread in that community link, you will get some pretty good insight on this Hope this helps.