When creating the Delimited File application, new identities are being created in the environment. However, my goal is for the imported accounts to be associated with existing identities that already have other aggregated accounts (such as Active Directory, HR application, etc.), so that I can reuse existing attributes like manager during the certification process.
I have the following questions:
Is there any key attribute that must be present in the file so that the account is correlated with an existing identity instead of creating a new one?
Or do I need to explicitly configure an Attribute Based Correlation to ensure this association? Or another configuration is needed?
Right now IIQ is just not able to match the incoming accounts to any existing identity, so it creates new ones.
To fix it, you need to give IIQ something common to match on — like employeeId or email — in your file, and then configure attribute-based correlation in the application.
Once that’s in place, IIQ will link the accounts to existing identities instead of creating new ones.
Yes — for a Delimited File source in SailPoint Identity Security Cloud, you typically need to configure correlation explicitly if you want the imported accounts to attach to existing identities instead of creating new ones.
The important part is having a common unique attribute between:
The file account
Existing identity/account data
Examples:
employeeId
email
username
workerId
Then configure:
Account Correlation / Attribute-Based Correlation in the source
Without proper correlation rules, ISC treats the imported records as new identities and creates separate identity profiles.
So in short:
Yes, the file should contain a reliable matching attribute
And you should configure Attribute-Based Correlation (recommended approach)
Also make sure the attribute values match exactly (case/format/whitespace), otherwise correlation may fail.
Hi @Nureen_Govan ,
From the target Delimited file application, if you want the accounts to be correlated to existing identities in SailPoint, you have to work on correlation logic.
If you have a matching unique attribute in target application accounts and the identity in SailPoint,. then it will be correlated.
If there is no direct attribute matching for the correlation,then try to implement a rule to correlate application accounts with identities.
Like Active Directory in your setup, this delimited application is no different. You need correlation logic that can cover maximum accounts of the target application.
For remaining accounts, you have option to create them as orphan in IIQ or ignore them i.e. not create orphan at all in IIQ (by configuring option to create link only if they can be correlated).
My recommendation would be to create orphan in IIQ so that you have visibility of the orphan accounts and work with application team to drive down the orphan count
Yes, the file should contain a reliable matching attribute