ISC sources marked as configuration incomplete in wrong edge case

Feedback General Feedback
1

Hi all :slight_smile:

We have a source that is completely working (and does not have the status Configuration Incomplete). All configuration is done and fine.
Sometimes the source can have many accounts, and sometimes it can have a lot.
It can even have no accounts at all at some.

But at moments where the source doesn’t have any accounts, it will be labeled as Configuration Incomplete. But all configuration (like correlation and schema’s) are properly configured.

I think this label should not be given if configuration is complete, but when no accounts exists. In IT terms, you could think of the array accounts: [{...},...,{...}] to mean that there are multiple accounts, accounts: [{...}] to mean that there is 1 account and accounts: [] to mean that there are 0 accounts. Only if we have accounts: null can we deduce that there is incomplete configuration. So there should be a distinguishment between account aggregation not being performed at all, or it being performed with 0 records as result. Similarly for delimited file sources where no account import was done v.s. one with an csv-import containing only the header.

We look at the label Configuration Incomplete to see which sources are still in progress on the application side. Now it will also have sources in here which were completely configured, but just doesn’t have any accounts (currently/anymore). This use case might also show up if you have a source where account aggregation is using a filter to only find troubled accounts. If they appear, we could perform actions, but if they are not there, we should not have it say that the source has incomplete configuration.

Kind regards,
Angelo

2

Hey @angelo_mekenkamp ,

Did you end up finding a workaround for this issue? We are seeing the same behavior for some of our sources and it is also triggering the Out of the Box Source Status Change email template repeatedly.

Seems like on top of the Configuration Incomplete label, SailPoint also marks these sources as being in an unhealthy state during the hourly source health check. Once the next aggregation runs and succeeds (but returns 0 accounts), the source briefly returns to a “healthy” before the next health check.

I know we can disable the health checks on sources but would rather not have to turn off the checks for each source we encounter this on.

Thanks,

Liam

3

@angelo_mekenkamp is there any resolution to this?

4

Hi @liamkokeeffe and @schattopadhy,

Thank you for your responses!

Unfortunately this is not resolved yet. We are dependant on SailPoint to change their logic here. A workaround could be to not trust the filtering on the SailPoint UI and instead run a script that will grab all the ones marked by SailPoint as configuration incomplete, and then perform checks such as performing test connection to determine if this is actually true.

@developer_advocates. Is this perhaps something you could advocate on behalf of us developers?

Kind regards,
Angelo