JDBC

The JDBC connector governs accounts and access stored in relational databases, homegrown applications, legacy systems, or any app whose access model lives in tables. You supply the SQL; SailPoint runs it for aggregation and provisioning.

The JDBC integration is a database connector. It connects via a JDBC driver using configurable SQL statements for reading and writing. As with every connector, the flow is the same: authenticate to JDBC, read accounts and entitlements during aggregation, and write changes during provisioning.

• 1. Configure the connection and credentials for JDBC.
• 2. Map the account schema, writing the aggregation query and mapping result columns to account and entitlement attributes.
• 3. Set the correlation logic so JDBC accounts attach to the right identities (typically on a stable key such as employee ID or email).
• 4. Run account aggregation and confirm accounts and entitlements load.
• 5. Verify correlation, watching for uncorrelated/orphan accounts.

You provide SQL for provisioning operations, create/update/delete/enable/disable, and SailPoint executes it as access changes are approved. This brings table-based access models under governance without application changes.

Entitlements are whatever the schema represents as access, rows in a roles table, flags, group columns. Map these deliberately and, where possible, normalise them into clear entitlement values.

When JDBC aggregation or provisioning fails, work through the usual causes in order:

• Verify the JDBC URL, driver and credentials.
• Confirm the database account has rights to run the aggregation and provisioning SQL.
• Check network/port access to the database.
• Validate that the SQL and column-to-attribute mapping are correct.

• Credential expiry (tokens/secrets/certs) silently breaking the connector.
• Insufficient rights on the JDBC service account for the operations you need.
• Schema or correlation misconfiguration leaving accounts uncorrelated.