JDBC Connector in SailPoint

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello,

In what scenarios do we use a JDBC connector? How can we determine an application is fit to be connected using a JDBC connector? Is there a template with questions that can be used to determine this?

Thanks,

Lakshmi.

Please consider addressing the following when creating your topic:

  • What have you tried?
  • What errors did you face (share screenshots)?
  • Share the details of your efforts (code / search query, workflow json etc.)?
  • What is the result you are getting and what were you expecting?
2

you would use the JDBC Connector if you need to read/write to databases, as listed on System Requirements

basically, its the “read/write via SQL queries!” commands connector.

1 Like
3

You would typically use a JDBC connector when the target system is a relational database such as Oracle, MySQL, Microsoft SQL Server, or PostgreSQL and you need to interact directly with user account data stored in database tables. It’s especially useful when the application doesn’t have a native SailPoint connector but exposes its data through SQL.

JDBC connectors are well suited for standard RDBMS table structures, but they’re also flexible enough to support more complex schemas using custom provisioning rules and tailored SQL queries.

When you talk to the application team, below could be your checklist to assess whether an application is a good candidate for JDBC integration or not:

  • Is the user account data stored in a relational database?
  • Can you access the database directly via JDBC?
  • Are the user account attributes (username, email, status, etc.) stored in a consistent and queryable format?
  • Does the table provide access/entitlement information in the same user table or a different table tied with the unique user id.
  • Is there an user attribute available to correlate user accounts to their identities in SailPoint? e.g., via employeeID, networkId (samaccountname) etc.

If the answer to most of these is a yes, then JDBC is likely a good fit.

To understand the connector in more detail, the official JDBC connector documentation is a good place to start. Many operations that previously required manual JDBC Prov rule writing are now streamlined and configurable directly through the UI. So if you’re exploring JDBC integration, definitely give the connector doc a read as it’d be of great help to you.

Thanks,

Arshad.

1 Like
4

Thank you @Arshad for the detailed response.

5

@Arshad - Do you have a similar checklist that can be used to identify if a system is fit to be connected via web services connector?

6

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.