We are observing a difference in how Identity Profile (IDP) connections are displayed for different source types in SailPoint ISC and would like clarification on the expected behavior.
Scenario:
We have multiple Non-Employee sources (connection type: Flat File).
In the Source → Connections → Identity Profile, it shows:
“There isn’t an identity profile associated with this source.”
However, in the Identity Profile API, these Non-Employee sources are clearly listed and actively used.
At the same time:
For other source types (e.g., Delimited, JDBC, AD, etc..), the **same Identity Profiles are visible at both levels
**
Is this difference in Identity Profile visibility expected behavior Non-Employee type sources?**
**
Thanks in advance!
Hello @vsuddala , SailPoint cannot differentiate a source as employee or non-employee until and unless if you have NERM module, it’s just authoritative source. Each authoritative source should have its own Identity Profile.
“There isn’t an identity profile associated with this source.”
Reason for above error at source level is, you haven’t configured/selected source in Identity Profile, but you have marked the source as authoritative during source creation. Just open the IDP and see if respective source has been selected.
Note: If you have marked source as authoritative, IDP needs to be configured for that source. Non-authoritative source doesn’t require IDPs.
In our case, the source is authoritative, and the Identity Profile is already configured and actively referencing the source. This can be verified from the IDP API at the attribute-transform level, for example: