JDBC Driver Enforcement Point
The eXate JDBC Driver is a client-side database driver that wraps standard Java Database Connectivity (JDBC) drivers to enforce centralised data security policies directly inside Java applications.
By acting as a proxy layer, the eXate JDBC driver intercepts standard database operations, rewrites SQL queries to apply Row-Level Security (RLS), and masks columns dynamically on the client side.
Key Capabilities
- Client-Side Enforcement: Performs SQL parsing, rewriting, and dynamic masking inside the application JVM, reducing database load.
- Seamless Drop-In Integration: Integrates into legacy and modern Java frameworks (e.g., Spring Boot, Hibernate, Apache Spark, Tomcat) by simply substituting the JDBC connection URL.
- Dynamic Access Control: Integrates directly with your identity provider to resolve user roles, department claims, and geographical context.
- Comprehensive Auditing: Captures and reports granular access logs directly from the application tier.
Integration Example
To activate the eXate JDBC Driver, you modify your application's database configuration to prefix the connection URL. For example:
Standard PostgreSQL Connection:
spring.datasource.url=jdbc:postgresql://localhost:5432/production_db
spring.datasource.driver-class-name=org.postgresql.Driver
eXate Protected Connection:
spring.datasource.url=jdbc:exate:postgresql://localhost:5432/production_db
spring.datasource.driver-class-name=com.exate.jdbc.ExateDriver
Technical Guides & Driver Setup
For detailed driver-level integration and database configuration walkthroughs, see the following guides:
- JDBC Driver Integration — Steps to integrate eXate into a new JDBC driver.
- MariaDB JDBC Driver — Detailed guide for installing and configuring the driver for MariaDB.
- PostgreSQL JDBC Driver — Detailed guide for installing and configuring the driver for PostgreSQL.
- Row & Column Level Security — Walkthrough of Row Level Security (RLS) and Column Level Security (CLS) enforcement.