Setting-up Kerberos Authentication¶
Several modules of the Denodo Platform support Kerberos authentication:
Diagnostic and Monitoring Tool
Scheduler and its administration tool
Before enabling Kerberos authentication on the Denodo Platform, you have to create a service account on the Active Directory of your organization and configure this account appropriately. This page explains how to do it.
Configuring the Kerberos Authentication Server (e.g. Active Directory)¶
You need to perform the following tasks on Active Directory (or the Kerberos server your organization uses). In many organizations, only the administrators of the Active Directory can do this.
Declare a Service Principal Name (SPN) and associate it with the user of the Virtual DataPort server.
Enable Kerberos delegation for this user account.
Optionally, on the computers where the Administration Tool of Virtual DataPort runs, modify the Windows registry to use the native ticket cache so the user does not have to enter her credentials when opening the administration tool.
After this, enable Kerberos authentication on the Denodo servers.
Create one account for each installation of the Denodo Platform: one account for the Denodo server for development, one for testing, etc.
We recommend all the components of an installation of the Denodo Platform to share the same account to make the configuration easier. That is, share the same keytab file and the same Service Principal Name (SPN).
If a Denodo installation is part of a cluster of Denodo servers and their client applications will connect to them through a load balancer, use the same account for all the installations of this cluster.
Creating a User in the Active Directory¶
Create a service account in Active Directory. This service account has to meet these requirements:
Create a User account, not a Machine account nor a Computer account.
Clear the option User must change password at next logon.
We recommend selecting Password never expires.
To do this in Active Directory, follow these steps:
Launch the tool Active Directory Users and Computers (in the menu Programs > Administrative Tools).
Right-click the Users node and click New > User (do not select Machine nor Computer).
denodo_server_productionin the Logon name field. You can enter a different name; the rest of the examples use “denodo_server_production”.
Click Next and enter a password.
denodo_server_productionin the Users tree, in the left side pane and double-click it.
Click the tab Account of “denodo_server_production” and in the panel Account options, do this:
We recommend selecting Password never expires. Otherwise, you will have to reconfigure and restart the Virtual DataPort server every time the password expires.
Regarding encryption mechanisms, we recommend clearing Use Kerberos DES encryption types for this account because is considered insecure.
We recommend clearing Account is sensitive and cannot be delegated. Otherwise, you will not be able to use Kerberos with constrained delegation, to pass-through the client credentials to underlying databases.
Declaring a Service Principal Name (SPN)¶
A Service Principal Name (SPN) is a unique identifier for a service running on a server. SPNs are used by Kerberos authentication to associate a service instance with a service logon account.
To define the SPN for Denodo, follow these steps:
Open a command prompt as an administrator, either from the host where the Denodo server is going to run or from the “Windows Domain Controller”.
With the utility
setspn, declare the SPN and associate it with the user account created in the previous step (“denodo_server_production”).
setspn -U -S HTTP/<Fully Qualified Domain Name of the Denodo server> <REALM>\<server account>
setspn -U -S HTTP/denodo-dv-prod.contoso.com CONTOSO.COM\denodo_server_production
The output should be like:
Checking domain DC=contoso,DC=com Registering ServicePrincipalNames for CN=Denodo Production Server,CN=Users,DC=contoso,DC=com HTTP/denodo-dv-prod.contoso.com Updated object
If you are doing this for a Denodo server that will be part of a cluster of Denodo servers and the client applications will connect to it through a load balancer, use the host name defined in the load balancer, not the actual host name of the Denodo server.
Verify that the user account only has one SPN. To do this, execute
setspn -L <user account>. For example,
setspn -L CONTOSO.COM\denodo_server_production
The output should be like:
Registered ServicePrincipalNames for CN=denodo_server_production,CN=Users,DC=contoso,DC=com: HTTP/denodo-dv-prod.contoso.com
Registered ServicePrincipalNames for CN=denodo_server_production,CN=Users,DC=contoso,DC=com: HTTP/denodo-dv-prod.contoso.com HTTP/denodo-dv-prod
Consider the following rules regarding SPNs:
In step #2, if
setspn -U -s ...returns an error like “Duplicate SPN found, aborting operation!”, it means this SPN is already registered, either on this account or another one. The SPN you use for Kerberos authentication of the Denodo servers cannot be associated with more than one user account. If it is, this authentication will not work.
The user account cannot be associated with two different SPNs either. If it is, the Kerberos authentication will fail for ODBC clients, web services, the Data Catalog, the Diagnostic and Monitoring Tool, and the Scheduler administration tool. The Denodo JDBC driver and the administration tool will be able to connect.
The SPN has to comply with the following rules:
The host name (in this example “host1.subnet1.contoso.com”) has to be the Fully Qualified Domain Name (FQDN) of the host where the Virtual DataPort server runs or in case of a cluster of Denodo servers, the FQDN defined in the load balancer for this cluster.
The “service class” of the SPN has to be
HTTP, except for the Scheduler server (it could be any string, for instance,
When web browsers request a Kerberos ticket, they do it for the service “HTTP/<host name of the URL you are accessing>” (the browser forms the SPN with “HTTP” even if you use the protocol “https”). The SPN of this ticket has to match the SPN that the Denodo servers will use; otherwise the authentication will fail.
If the SPN does not meet these rules, the Kerberos authentication will fail for ODBC clients, web services, the Data Catalog, the Diagnostic and Monitoring Tool, and the Scheduler administration tool. The Denodo JDBC driver and the administration tool will be able to connect.
SPNs are case insensitive when used by Microsoft Windows-based computers. However, Linux/Unix is case-sensitive and requires the proper case to function properly. So, when you create the SPN and configure the Virtual DataPort server, always enter the SPNs with the proper case. That is, the host name in lower case (e.g. denodo-prod.subnet1.contoso.com) and the domain name in upper case (e.g. CONTOSO.COM).
If your organization uses Microsoft Active Directory 2003 or earlier, you cannot use the -S switch in setspn because it is not available for that version. In that case, replace -S with -a but make sure that the same SPN is not associated to two user accounts.
See the documentation of
See what a Fully Qualified Domain Name is at https://en.wikipedia.org/wiki/Fully_qualified_domain_name.
Enable Kerberos Delegation for this User Account¶
You need to do this step if:
You plan on enabling Kerberos authentication on any of the following components of Denodo: Data Catalog, Scheduler or Web Panel.
Or you plan on creating JDBC data sources that use the option “pass-through session credentials” and Kerberos authentication.
If you are not going to do any of these things, jump to the next section. You can do these changes in the future.
ktpass, two things change in the configuration of the user account in Active Directory:
In the Account tab, the field User logon name changes to the Service Principal Name (before, it was just the name user account).
There is a new tab: Delegation.
Follow these steps:
Open the new user account and go to the tab Delegation.
Select one of these options:
Trust this user for delegation to any service (known as “open delegation”). With this option, Active Directory will allow Virtual DataPort to delegate to any service (database, web service…) the Kerberos credential that the user used to connect to Virtual DataPort. In addition, it will allow the Data Catalog and Scheduler to connect to Virtual DataPort using Kerberos authentication.
Trust this user for delegation to specified services only (known as “constrained delegation”). If you select this, you also have to do this:
Select Use any authentication protocol. Otherwise, the pass-through session credentials of Kerberos will not work.
In the list Services to which this account can present delegated credentials, add the following:
The SPN (Service Principal Name) of this same user (e.g.
HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM). That way, if you enable Kerberos authentication on the Data Catalog or Scheduler, these components can delegate to Virtual DataPort the Kerberos credential of the user.
The SPNs (Service Principal Names) of the databases and web services to which you want to allow Denodo to delegate the Kerberos credentials that the user used to connect to Virtual DataPort.
With the option Trust this user for delegation to specified services only, Active Directory will allow Virtual DataPort - and any other Denodo components that use the same SPN - to delegate the Kerberos credentials of the users only to the services on this list.
If you select Trust this user for delegation to specified services only, you are enabling “constrained delegation”. That is, the queries sent to Virtual DataPort will fail if they involve a JDBC data source with the authentication option “pass-through session credentials” and the driver does not support Kerberos authentication with constrained delegation. Read the section Connecting to a JDBC Source with Kerberos Authentication of the Administration Guide to check if in your scenario, you can enable this option.
Generating a Keytab File¶
After defining the SPN, generate a keytab file. A keytab file contains pairs of Kerberos principals and encrypted keys derived from the password of a user account. The Denodo components (Virtual DataPort, Scheduler…) will use this keytab to authenticate themselves with Active Directory. Once they are authenticated, they can authenticate other users.
From the command line of the Windows Domain Controller, execute this (only domain administrators can run it):
ktpass /out denodo.keytab /princ <SPN with FQDN>@<REALM> /mapUser <server Active Directory account> /crypto ALL /pass * /ptype KRB5_NT_PRINCIPAL
ktpass /out denodo_server_production.keytab /princ HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM /mapuser denodo_server_production /pass * /crypto ALL /ptype KRB5_NT_PRINCIPAL
You will have to enter the password of the user account “denodo_server_production”.
Make sure the password entered is correct and the case of the principal is the right one. ktpass does not validate this. It just generates the keytab based on the principal and the password you enter.
You should see something like:
Successfully mapped HTTP/denodo-dv-prod.contoso.com to denodo_server_production. Type the password for HTTP/denodo-dv-prod.contoso.com: Type the password again to confirm: Password succesfully set! Key created. Key created. Key created. Key created. Key created. Output keytab to denodo.keytab: Keytab version: 0x502 keysize 70 HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM ptype 1 (KRB5_NT_PRINCIPAL) vno 4 etype 0x1 (DES-CBC-CRC) keylength 8 (0xfbeaece643fef213) keysize 70 HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM ptype 1 (KRB5_NT_PRINCIPAL) vno 4 etype 0x3 (DES-CBC-MD5) keylength 8 (0xfbeaece643fef213) keysize 78 HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM ptype 1 (KRB5_NT_PRINCIPAL) vno 4 etype 0x17 (RC4-HMAC) keylength 16 (0x25e19011618301a73e20fda538e18a91) keysize 94 HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM ptype 1 (KRB5_NT_PRINCIPAL) vno 4 etype 0x12 (AES256-SHA1) keylength 32 (0x0370175225b496a88a120973d70e28bb9e94f113a2b827926ad52d093471f35f) keysize 78 HTTP/denodo-dv-prod.contoso.com@CONTOSO.COM ptype 1 (KRB5_NT_PRINCIPAL) vno 4 etype 0x11 (AES128-SHA1) keylength 16 (0x60c3d8c6f43727deeaccc480f8101c41)
See more about “ktpass” in its documentation.
Distribute the Keytab and Enable Kerberos Authentication on Denodo Servers¶
Copy the file “denodo_server_production.keytab” to the computer where you installed the Denodo Platform. If this server is part of a cluster of Denodo servers, copy it to all these computers.
After this, enable Kerberos authentication on the modules required. See:
For Virtual DataPort, see the page Kerberos Authentication.
For Scheduler, see the page Kerberos Configuration.
For Data Catalog, see the page Kerberos Configuration.
Kerberos authentication on the Diagnostic & Monitoring Tool is enabled automatically when you enable it on Virtual DataPort.
Deal with the keytab with the same precautions you use when dealing with passwords. That is, do not store them in a file share, when copying to a Denodo installation, change the privileges of the file so it can only be accessed by the user account that launches the Denodo components, etc.
Modifying the Windows Registry to Use the Native Ticket Cache¶
The Virtual DataPort administration tool and the Denodo JDBC driver provide “Single Sign-on” (SSO), which means that the users do not need to enter their password to log in.
If the administration tool runs on Windows with the Denodo update 20190312 or earlier, and you want to use this feature, you have to modify the Windows registry of the host where the tool runs. That way, the tool will be able to obtain the Kerberos ticket that the system acquired when you logged in to the system. The reason for having to modify the registry to use SSO is that Microsoft added a new feature in which they no longer export the session keys for Ticket-Granting Tickets (TGTs). As a result, the native TGT obtained on Windows has an “empty” session key and null EType. If the administration tool has the update 20190903 or newer, you do not need to do this.
You do not have to do anything to use single sign-on on Linux or to connect to the Denodo server using the ODBC driver.
Jump to the next task if you are not going to use “single sign-on” or the administration tool runs on Linux.
Note that you can use Kerberos authentication without modifying the registry by providing the user and the password when you log in. This is what you do when selecting Use user/password of the Kerberos authentication options of the administration tool.
To modify the registry, follow these steps:
Look for the key
Right-click the “Parameters” node and click New > DWORD.
Enter the name of the entry:
Double-click the new entry and set the value to
You have to do this in all these hosts:
All the hosts where Virtual DataPort administration tools run and whose users want to use Kerberos authentication.
All the hosts where JDBC clients run and want to use Kerberos authentication.
You have to do this when the client runs on Windows because, as explained in the Troubleshooting page for Kerberos authentication of the Java Runtime Environment, Windows does not give access to the session key of a Ticket-Granting Ticket (TGT) by defaults. This change in the registry will make the session key for TGT accessible, so Java can use it to acquire additional service tickets.
Even if you modify the registry, if the user that starts the administration tool belongs to the group “local administrator” of that computer, the tool will not be able to retrieve the Kerberos ticket from the system. This will make the single sign-on to fail. If that is the case, use the options Use user/password or Use ticket cache of the Kerberos authentication options of the administration tool.
The information provided in this section also applies to the Denodo JDBC driver.