Understanding the Correlation Logic
System uses correlation rule to match accounts with existing identities
If an account is uncorrelated a new identity is created using ApplicationName+saMAccountName
Observed issue
When the correct data is available in the uncorrelated account to match an existing identity attribute,It does not correlate to existing Identity
Instead,It always correlates to newly created identity(ApplicationName+saMAccountName)
However,if this newly created identity is deleted,the account correctly correlates to the intended existing identity.
Expected Behaviour:
The system Should correlate the account to existing identity if the correct attributes are available
Dont want to do Manual Correlation.
I try with checking disable optimization accounts in aggregation as well but issue persist same
Hi @DMalaghe1993 , You can use correlation logic in correlation rule at connector level resolve your issue.
Thanks,
@SivaLankapalli
@SivaLankapalli Can you explain me more about it
Hi @DMalaghe1993 , I understand you’re trying to aggregate authoritative sources.
I hope you have configured the correlation mapping or correlation rule in aggregation rules.
if you did not mention any correlation configuration based on desired attributes mapping. connector always use identity Display Attribute to correlate.
I hope this helps. If possible, please share the application.xml file for review.
Thanks,
@SivaLankapalli
@SivaLankapalli Thanks its issue with correlation rule logic
system
(system)
Closed
April 14, 2025, 5:53am
6
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.