GSSAPI Authentication with MariaDB Connector/J

MariaDB has supported GSSAPI authentication since when the authentication plugin was added.

The subsections below describe how to configure and use GSSAPI authentication with MariaDB Connector/J:

Support history,

• version 1.4.0 : java connector support

• Version 1.5.0: added native Windows implementation.

General configuration

The authentication plugin must be installed on the database server. The relevant user account must also be configured to use the plug-in for authentication.

For example:

And then this user account could be used to connect to the database server with the Java connector by specifying the user name in the Java connection URL.

For example:

Since the user account is configured to use the authentication plugin on the server, the Java connector will use GSSAPI authentication when connecting.

The service principal name must be the one defined for the user account on the database server unless a different one is specified with the parameter in the connection URL.

The database server will wait for a ticket associated with the principal defined in the user ('userOne@EXAMPLE'). It means on the client, the user must have obtained a TGT beforehand.

As part of the security context establishment, the driver will initiate a context that will be authenticated by the database. The database is also authenticated back to the driver ("mutual authentication").

GSSAPI configuration

Java system properties

Realm information is generally defined by DNS, but this can be forced using system properties. "java.security.krb5.kdc" defined the Key Distribution Center (KDC), and the realm was defined by "java.security.krb5.realm". Example :

Logging can be set using additional properties:

Java JCE

Depending on the Kerberos ticket encryption, you may have to install the Unlimited Strength Jurisdiction Policy File. (CentOS/Red Hat Enterprise Linux 5.6 or later and Ubuntu are using AES-256 encryption by default for tickets).

On Unix, you can execute the "klist -e" command to view the encryption type in use: If AES is being used, output like the following is displayed after you type the klist command (note that AES-256 is included in the output):

Implementations

On Windows, the GSSAPI implementation is SSPI. The Java 8 native implementation has many limitations ().

The driver contains 2 different implementations:

• A Java standard implementation will use JAAS to allow Java to access TGT.

• A windows native implementation based on

Standard java SSPI implementation

Jaas

The driver will use the native ticket cache to get the TGT available in it using JAAS. If the system property "java.security.auth.login.config" is empty, the driver will use the following configuration:

This permit to use the current user TGT cache

limitation on windows

Main limitations are:

• To permit Java to retrieve TGT (Ticket-Granting-Ticket), the windows host needs to have a registry entry set.

• The Kinit command must have been executed previously to the connection.

Windows native java implementation

Implementation is based on that supports Windows SSPI based on .

If waffle-jna (and dependencies) is in the classpath, the native implementation will automatically be used. (This permit to avoid any specific problem with admin right, registry, kinit ...)

Dependencies:

Possible errors

• "GSSException: Failure unspecified at GSS-API level (Mechanism level: No Kerberos credentials available)"

There is no active credential. Check with Klist that there is an existing credential. If not, create it with the "kinit" command

• "java.sql.SQLInvalidAuthorization SpecException: Could not connect:GSSAPI name mismatch, requested 'userOne@EXAMPLE.COM', actual name 'userTwo@EXAMPLE.COM'.

There is an existing credential, but it doesn't correspond to the connection user. example: if user is created with a command like

klist must show the same principal (userTwo@EXAMPLE.COM in this example)

• "GSSException: No valid credentials provided (Mechanism level: Clock skew too great (37))." The Kerberos protocol requires the time of the client

and server to match: if the system clocks of the client do not match that of the KDC server, authentication will fail with this kind of error. The simplest way to synchronize the system clocks is to use a Network Time Protocol (NTP) server.