Most JDBC Clients

For most JDBC clients, the configuration enabling the JDBC client to participate in Kerberos authentication can be done in the start script or a configuration file of the JDBC client. If the JDBC client requires a username and password to be specified, you can provide bogus/dummy values for both.

The settings are added via the start script or configuration file:

TEXT

-Djavax.security.auth.useSubjectCredsOnly=false
-Dsun.security.jgss.native=false  
-Djava.security.krb5.realm=<...>
-Djava.security.krb5.kdc=<...>
-Djava.security.auth.login.config=path\to\dvclient.conf

Please note that <realm> is the name of your Kerberos realm.

Here is an example:

TEXT

-Djavax.security.auth.useSubjectCredsOnly=false
-Dsun.security.jgss.native=true
-Djava.security.krb5.realm=KRBTEST.DV
-Djava.security.krb5.kdc=DC01.KRBTEST.DV
-Djava.security.auth.login.config=c:\datavirtuality\dvclient.conf

And here are some examples of JDBC clients which can be set up in this way:

CData Virtuality Studio with the configuration file dvstudio.ini
DBeaver with the configuration file dbeaver.ini
Squirrel with the start script squirrel.bat

Please note that this way of configuration does not work for Tableau Desktop. For information on how to set up Tableau Desktop, please refer to this page.

The mandatory steps for all JDBC clients participating in Kerberos authentication are described here.