You can configure account correlation logic per source. You can add multiple correlation steps if you want. However, if correlation on those steps does not result in a match, instead of marking the accounts as uncorrelated, a hidden correlation step occurs. This step currently can not be disabled, removed or changed, even when using a correlation rule. This is quite annoying for us, as it actually limits the functionality. If it wasn’t there, we could have added it ourselves, but now it is there, we can’t get rid of it.
Sorry, no workaround available. This issue still exists. Please reach out to your Customer Success Manager to hopefully get even more outreach
I understand SailPoint trying to put default functionality in place to speed up our implementations, but if they are not allowing to overwrite this default configuration all they do is put limitations on their own functionality.
I see a pattern of SailPoint making this (in my opinion) mistake. For other examples, I did see announcements like (only paraphrasing):
“We allow you to configure which identity attributes are visible for approvers, we notice that many organizations want the email address visible, so we will add it for you directly, and oh yeah, you are not able anymore to remove this configuration.”
It all boils down to: One size fits nobody. Keep supporting configuration is good
