Download | Release Notes | Changelog |

Release date: 27 Jan 2020

MariaDB Connector/J 2.5.4 is a Stable (GA) release.

Notable Updates

• - Logging correction when using enablePacketDebug option

• - permits to avoid setting session_track_schema with new option trackSchema

Changelog

For a complete list of changes made in MariaDB Connector/J 2.5.4, with links to detailed information on each push, see the .

Download | Release Notes | Changelog |

Release date: 22 Nov 2019

MariaDB Connector/J 2.5.2 is a Stable (GA) release.

Notable Updates

• - use pool reset only for corrected COM_RESET_CONNECTION

• - byte signed value wrong serialization for text protocol

• ensure plugin using Driver classloader

Changelog

For a complete list of changes made in MariaDB Connector/J 2.5.2, with links to detailed information on each push, see the .

| Release Notes | |

Release date: 8 Jan 2020

MariaDB Connector/J 2.5.3 is a (GA) release.

Notable Updates

Download | Release Notes | Changelog |

Release date: 16 Oct 2019

MariaDB Connector/J 2.5.1 is a Release Candidate (RC) release.

Notable Updates

• - Error packet caching_sha2_password not handled when not having a password

• - PAM authentication multiple exchanges permitting multiple steps in connection string

• - Multi insert regression correction returning multi generated keys

• - OSGI compliance

Changelog

For a complete list of changes made in MariaDB Connector/J 2.5.1, with links to detailed information on each push, see the .

Download | Release Notes | Changelog |

Release date: 3 Oct 2019

MariaDB Connector/J 2.5.0 is a Release Candidate (RC) release.

Evolutions

Authentication service

are now defined as services. This permits to easily add new client authentication plugins. The driver has 2 new plugins caching_sha2_password and sha256_password plugin for MySQL compatibility

List of authentication plugins in java connector :

• mysql_clear_password

• auth_gssapi_client

• client_ed25519

• mysql_native_password

New authentication plugins can be created implementing interface org.mariadb.jdbc.authentication.AuthenticationPlugin, and listing new plugin in a META-INF/services/org.mariadb.jdbc.authentication.AuthenticationPlugin file.

Credential service

Credentials are usually set using user/password in the connection string or by using DriverManager.getConnection(String url, String user, String password).

Credential plugins permit to provide credential information from other means. Those plugins have to be activated setting option credentialType to designated plugin.

The driver has 3 default plugins :

AWS IAM

This permits AWS database IAM authentication. The plugin generate a token using IAM credential and region. Token is valid for 15 minutes and cached for 10 minutes.

To use this credential authentication, com.amazonaws:aws-java-sdk-rds dependency must be registred in classpath. Implementation use SDK DefaultAWSCredentialsProviderChain and DefaultAwsRegionProviderChain to get IAM credential and region. see and to check how those information can be retrieved (environment variable / system properties, files, ...)

Example: jdbc:mariadb://host/db?credentialType=AWS-IAM&useSsl&serverSslCert=/somepath/rds-combined-ca-bundle.pem

with AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_REGION environment variable set.

Environment

User and Password are retrieved from environment variables. default environment variables are MARIADB_USER and MARIADB_PWD, but can be changed by setting additional option userKey and pwdKey

Example : using connection string jdbc:mariadb://host/db?credentialType=ENV user and password will be retrieved from environment variable MARIADB_USER and MARIADB_PWD.

Property

User and Password are retrieved from java properties. default property name are mariadb.user and mariadb.pwd, but property names can be changed by setting additional option userKey and pwdKey

Example : using connection string jdbc:mariadb://host/db?credentialType=PROPERTY&userKey=mariadbUser&pwdKey=mariadbPwd user and password will be retrieved from java properties mariadbUser and mariadbPwd

SSL factory service

A connection to a server initially creates a socket. When set, SSL socket is layered over this existing socket. Implementing org.mariadb.jdbc.tls.TlsSocketPlugin permit to provide custom SSL implementation for example create a new implementation.

Custom implementation need to implement org.mariadb.jdbc.tls.TlsSocketPlugin and register service META-INF/services/org.mariadb.jdbc.tls.TlsSocketPlugin

Custom implementation are activated using option tlsSocketType

Other

• : JDBC 4.3 partial implementation java.sql.Statement methods isSimpleIdentifier, enquoteIdentifier, enquoteLiteral and enquoteNCharLiteral

• : ConnectionPoolDataSource interface addition to MariaDbPoolDataSource

• : closing possible option batch thread on driver deregistration.

Bug fixes

• : Driver getPropertyInfo returns no options information when url is empty

• : DatabaseMetaData.getSchemaTerm now return "schema", not empty string

New options

Changelog

For a complete list of changes made in MariaDB Connector/J 2.5.0, with links to detailed information on each push, see the .