Hi team,
Is there any way to brings only correlated account in Sailpoint ISC.
Hi team,
Is there any way to brings only correlated account in Sailpoint ISC.
@Faizan854187 SailPoint ISC can determine whether an account is correlated or not, only after it has been aggregated into the ISC system and evaluated against the defined correlation configuration.
But by default, aggregation brings in all accounts from the target system. However, if you want to limit the scope, you can apply account-level filtering to exclude specific accounts from aggregation based on predefined criteria.
You cannot selectively bring in only correlated accounts, as correlation is determined after aggregation within the ISC system.
Hi @Arshad ,
Is it is possible in IIQ
Even in IIQ, the behavior is quite similar where the aggregation first brings in all accounts from the target source, and then correlation rules determine which of those accounts link to existing identities.
Even there, you might need to have an ‘Account Selection Rule’ during aggregation to pre-filter the accounts based on certain attributes which is similar to what we can do on ISC as well as explained above with correlation rules.
But however, I’m not really an IIQ expert so can’t exactly comment on this for sure.
Thanks alot @Arshad for clarification.
HI @Arshad Is is possible to delete the uncorrelated records from that source by any rule or any other ways.
You can clear existing one time manually then you have an option is aggregation task create links only if correlated use that option and it won’t create uncorrelated accounts in IIQ anymore I guess.
I know the question has been answered, but it leaves me with the question: what is the use case for this? Kind of defeats the purpose of an IGA platform, IMHO.
Hi Jeremy,
The requirement is that the client wants that no uncorrelated account should come in their system.
Hi Pradeep,
You have any idea how we can achieve this use case in ISC. Any rule or any string filter we can put once we delete the uncorrelated account manually in ISC so that when we re-run aggregation it should not come
Hi Faizan,
That solely depends on the connector type you are using.
You can try filterString but that totally depends on connector type. Some connectors does not support it.
Thanks
Pradeep
Hi Faizan
Sorry I replied earlier in context of IIQ. I am not sure if Only Create on Correlation option is available in ISC.
Sorry about the confusion.
No Worries Pradeep .
Hi pradeep, Just want to check one thing. Can we delete the uncorrelated account after every aggregation automatically through rule script or workflow. Any idea how we can achive this use case.
It most certainly defeats the purpose
If I did everything a client told me to do, then I would be failing at one of the more important aspects of client based work, and that’s helping them to follow best practices. Clients have lots of ideas, and not all of them are good. It’s our job as SMEs to help them understand why taking a certain action isn’t in their best interest instead of just implementing whatever they ask for