An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.

Version 6.0.0

ENHANCEMENTS

• The driver has been enhanced to support the TLSv1.3 cryptographic protocol. As part of this enhancement, the default cryptographic protocol enabled by the driver has been updated to TLSv1.3. For details, refer to CryptoProtocolVersion.*
• The driver has been enhanced to support the Generic Security Standard (GSS) 
  plug-in for authentication. The plug-in consists of a set of APIs that you can
  implement to customize your authentication requirements and interoperate with 
  various security methods. You can configure a GSS plug-in using the refreshed 
  AuthenticationMethod property and the new GSSPluginName and GSSPluginObject properties. For details, refer to AuthenticationMethod, GSSPluginName, and GSSPluginObject.
• The driver has been enhanced to support connecting to a proxy server through
  an HTTP connection. HTTP proxy support is configurable with the new 
  ProxyHost, ProxyMode, ProxyPassword, ProxyPort, and ProxyUser connection 
  properties. For details, refer to Connection Properties.
• The KeepAlive connection property has been added to the driver. Enabling the
  KeepAlive property allows the client to keep idle TCP connections active by periodically passing packets to the server. For details, refer to KeepAlive.
• The driver has been enhanced to support Windows Defender Credential Guard when using Kerberos Authentication. For details, refer to Configuring Kerberos Authentication.
• Interactive SQL for JDBC is now installed with the product. It is a command-line interface that supports connecting your driver to a data source, executing SQL statements and retrieving results in a terminal. This tool provides a method to quickly test your drivers in an environment that does not support GUIs.
• Added the RegisterStatementPoolMonitorMBean connection property. Note that the
  driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
  You must set RegisterStatementPoolMonitorMBean to true to register the Statement Pool Monitor and manage statement pooling with standard JMX API calls. For details, refer to RegisterStatementPoolMonitorMBean.
• Support for cursor type OUT parameters for DB2 for Linux, UNIX, Windows stored procedures has been added to the driver.

CHANGED BEHAVIOR

• The TLSv1.1 and TLSv1.0 cryptographic protocols are now disabled by default. These protocols are no longer considered secure and, therefore, are no longer recommended for use. However, the driver still supports TLSv1.1 and TLSv1.0 for legacy servers that do not support more secure protocols. For details, refer to CryptoProtocolVersion.*
• The SSLv3 and SSLv2 cryptographic protocols are no longer supported.*
• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.*
  Note: This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  Available: July 3, 2024
• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.
• For DB2 for z/OS, the AlternateID connection property has been modified to set the name of the schema in the DB2 CURRENT SCHEMA special register instead of the DB2 CURRENT SQLID special register. AlternateID now sets the name of the schema in the CURRENT SCHEMA special register for DB2 for i, DB2 for Linux/UNIX/Windows, and DB2 for z/OS. For details, refer to AlternateID.

Version 5.1.4

ENHANCEMENTS

• The driver has been enhanced to include timestamp in the Spy and JDBC packet
  logs by default. If required, you can disable the timestamp logging by
  specifying the following at connection: For Spy logs, set
  spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
  set ddtdbg.ProtocolTraceShowTime=false.*
• The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability. For details, refer to CryptoProtocolVersion.
• The connection properties RandomGenerator and SecureRandomAlgorithm have been
  added to the driver.
  • RandomGenerator allows you to specify the type of random number generator (RNG) the database uses for secure seeding.
  • SecureRandomAlgorithm can be used to specify the SecureRandom number generation algorithm used for secure seeding with implementations of JDK 8 or higher when RandomGenerator is set to secureRandom.
  For details, refer to RandomGenerator and SecureRandomAlgorithm.
• Support for result set holdability has been added to the driver.

Version 5.1.3

No new features 

Version 5.1.2

No new features

Version 5.1.0

No new features