Exasol supports single-sign functionality using Kerberos. By supporting Kerberos based single sign-on (in JDBC and ODBC), users can authenticate to Exasol using their Kerberos credentials. This allows for a seamless user experience.
Kerberos is centered around its Key Distribution Center(KDC). To use Kerberos based single sign-on in Exasol, a keytab file must be provided by your Key Distribution center or by your Active Directory administrator for Windows system. This keytab file consists of the service principles for Exasol databases. This keytab file is uploaded through EXAoperation.
Enable Kerberos in Exasol
You can follow the below steps to enable Kerberos in Exasol.
- In EXAoperation, go to Services > EXASolution and select the database name to open EXASolution Instance for it.
- Shut down the database if it is running by selecting Shutdown from the Actions... drop down list and click Submit. Wait until the database is offline.
- Upload the keytab file to be used in the cluster. Click the Browse button located at the bottom and then click Upload Keytab File.
- As an optional step after you have uploaded the keytab file, you can set additional parameter values. Click Edit to edit the database and set the values for the following parameters:
- Kerberos Service Name
- Kerberos Host Name
- Kerberos Realm
Setting these values are optional. For a brief description of these parameters, refer to the Kerberos Parameters table below.
Click Apply and then start the database.
|Kerberos Service Name||
If a Kerberos Service name is specified, then only the specified Kerberos service can be requested by the client. If there is no service name specified, then all the service requested by the client is accepted provided the service exists in the keytab file uploaded.
The default service name is exasol.
|Kerberos Host Name||
If a hostname is specified, then only that hostname is accepted by the client, regardless of whether the uploaded keytab file contains entries for other hostnames.
The host name of the Kerberos principal is valid cluster-wide, which means it can be considered virtual. If no hostname is specified, then the hostname will not be checked during Kerberos authentication.
If a Kerberos realm is specified, then only users of this realm will be accepted, regardless of whether the uploaded keytab contains entries for other realms.
If no Kerberos realm is specified, then by default users from all the realms are accepted, provided there is an entry of the realm in the keytab file.