Tenant-Based Checksum Management
The system allows the upload of product-certified JDBC drivers, as well as tenant-based checksum management, where you can manage and certify your own JDBC driver jar for upload.
Overview
This dual-checksum architecture enables you to manage your own certified JDBC drivers while maintaining a reliable fallback to system-certified drivers. The system-certified checksum is read-only, while the tenant-specific checksum can be managed by an administrator.
Uploading a Driver JAR
When uploading a driver, the driver checksum is validated against the certified checksum, and only certified jars are allowed for upload.
Impact on connections:
- Existing connections continue to operate without any changes.
- New connections are not affected by the addition.
- Connection restarts proceed normally.
- The new driver becomes available only when explicitly selected and configured.
Adding a New Checksum Entry
When an administrator adds a new checksum entry for a JDBC driver JAR, the driver becomes certified and trusted for upload. A tenant user can then upload and configure the new driver for connections.