About JDBC Proxy Driver

Delinea's JDBC Proxy Driver is used to securely and automatically manage database server credentials stored inside the Java web application configuration file. This approach enables organizations to follow internal and regulatory compliance requirements of periodic password replacement and eliminates downtime without restarting the application server.

You can integrate your web application with Delinea solutions via JDBC Proxy Driver, including the Delinea Platform and Secret Server, to retrieve database credentials from the application configuration file using the JDBC Proxy Driver. Once retrieved, these credentials can be used to securely connect to your database.

Supported Web Servers

The following web server integrations are available for both Delinea Platform and Secret Server:

The integration is not affected when Delinea deprecates some Java APIs, and the Delinea JAR file works with the current Java version.

Database Connection Approaches

The Delinea JDBC Proxy Driver supports two database connection approaches: Direct Connection and DataSource Connection. You only need to choose and configure ONE approach based on how your application currently connects to the database.

Choose Your Connection Approach

Select the approach that matches your application's database connection method:

Direct Connection

Use this approach if:

Your application reads database configuration (username, password, driver URL) directly from the application's configuration file
Your application creates connections using DriverManager.getConnection() or similar methods
Database credentials are specified in application properties files (e.g., persistence.xml, application.properties)

How it works: The Java application requests the Delinea JDBC Proxy Driver to fetch the database credentials from Secret Server or Delinea Platform. When a database credential is fetched, the Delinea driver passes the credential to the native driver (for example, MySQL, SQL Server) and makes a connection with the database.

DataSource Connection

Use this approach if:

Your application performs JNDI lookup to obtain database connections.
Your web server manages the database connection pool.
DataSource configuration is defined in server configuration files (e.g., Tomcat's context.xml, WebSphere's server.xml, JBoss's standalone.xml)

How it works: The Java application looks up the Delinea DataSource and calls the Delinea JDBC Proxy Driver to fetch the database credentials from Secret Server or Delinea Platform. The JDBC Proxy Driver looks up the native driver and connects to the database.

DataSource Connection Types

If you choose DataSource Connection, you must also select the appropriate transaction type:

Non-XA DataSource - For standard single database transactions (most common use case)
XA DataSource - For distributed transactions across multiple databases, JMS, or other resources requiring two-phase commit