In all cases, it is a best practice to configure all JDBC connections with the minimal properties required for the application and server to function. When configuring properties, users should avoid configuring properties with a wide scope (e.g. or those that can be set by any authenticated user (e.g. jdbc/user/pass). A last resort defensive measure to block the pgjdbc driver is to place a deny statement in your application's security configuration (e.g. filter> or mapping> sections). REQ. A vendor-supported way to disable the driver.

Requirements of the Security Configuration

The pgjdbc driver will not function if there is a security configuration that denies the driver from accessing a JDBC connection.

Vendor-supplied FQDN, port and SSL/TLS fingerprint

The pgjdbc driver is typically installed with a vendor-supplied FQDN (i.e., port number (i.e. 5432) and SSL/TLS certificate fingerprint (i.e. 1F8:48:81:B6:0D:C2:FF). Vendors typically include these in the default configuration files shipped with the driver, and users should not modify them as they are required by the JDBC specification for authentication purposes and may vary based on the configuration of the application server or database service being connected to.




Published on: 03/10/2022 17:47:00 UTC
Last modified on: 08/01/2022 11:15:00 UTC