SQL Loader issue for provisioning

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hey Team ,

Integrated SQL Loader connector and also try to provision account into it and it is showing success (completed) through access request center.But while aggreagtion that account is not cmoming into sailpoint ? Any idea

2

Hi @Rakesh_Singh_1234 ,

If provisioning is showing as successful but the account isn’t appearing after aggregation, I’d first check whether the account was actually created in the target SQL table.

Also verify:

  • The aggregation query returns the newly created record.
  • There are no filters excluding the account during aggregation.
  • The native identity/account ID is populated correctly.

In most cases, either the account wasn’t created as expected or the aggregation query isn’t picking it up.

Thanks.

3

For SQL loader, provisioning updates are not performed by the OOTB connector. We need a JDBC provisioning Rule to execute the insert/update/delete operations.

Verify the JDBC provisioning Rule is attached to the source and that it is executing the required write operations.

refer :

4

Hi @Rakesh_Singh_1234

A few things to check:

  • The access request shows Completed in ISC, but that does not necessarily mean the account was created in the target database.

  • For SQL Loader/JDBC sources, account provisioning requires a JDBC Provisioning Rule to perform create/update operations on the target system.

  • If the JDBC Provisioning Rule is not configured, provisioning is completed only within ISC and no account is created in the target.

  • During the next aggregation, ISC looks for the account in the target system.

  • Since the account does not exist in the target, it is not aggregated back into ISC and may be removed from the source accounts.

I would recommend verifying whether a JDBC Provisioning Rule is configured and checking if the account was actually created in the target database.

5

Please check this link