Pre-requisites for Kerberos integration

Before you begin, please verify the following:

1. The

   D s defaultuser
   Type hadoop Full true

   user is created and enabled on each node in the Hadoop cluster.

   Info
   NOTE: If LDAP is enabled, the D s defaultuser Type hadoop Value true should be created in the same realm as the cluster.

2. On the 

   D s item
   item host

   , the directory /opt/trifacta is owned by the

   D s defaultuser
   Type hadoop

   user.

3. The

   D s defaultuser
   Type hadoop

   user exists on each node in the Hadoop cluster.

   Info
   NOTE: The D s defaultuser Type hadoop must have the same user ID and group ID on each node in the cluster. Depending on your cluster's configuration, this requirement may require an LDAP command. Configuring LDAP is beyond the scope of this document.

4. The

   D s defaultuser
   Type hadoop

   user must be a member of any special group that is permitted to access HDFS or to run Hadoop jobs.

Configure the KDC

Steps:

1. On your KDC node, configure a Kerberos principal for the 

   D s platform

   :
   1. The principal's identifier has two parts: its name and its realm. For example, the principal trifacta@HADOOPVAL.MSSVC.LOCAL has the name trifacta and the realm HADOOPVAL.MSSVC.LOCAL. 
   2. Retain the name and principal for later configuration.

2. Create a keytab file for the 

   D s item
   item principal

   . Command:
   

   Code Block
   kadmin xst -k trifacta.keytab <full principal identifier>

   where:
   <full_principal_identifier> is the principal identifier in Kerberos. 
   

   Warning
   On the KDC, you may have to run kadmin.local instead of kadmin. The rest of the arguments should remain the same.

   Info
   NOTE: If you're creating a keytab file in an AD environment, alternative instructions may need to be applied. See below.

3. Verify that the keytab is working. Command:
   

   Code Block
   klist -e -k -t trifacta.keytab

4. Copy the keytab to the 

   D s item
   item node

    in the following directory: 
   /opt/trifacta/conf/trifacta.keytab
   

5. Configure the keytab file so that it is owned by the

   D s defaultuser
   Type hadoop

   user. It should only be readable by that user.
   

   Info
   NOTE: Verify that all user principals that use the platform are also members of the group of the keytab user.

Create keytab in Active Directory environments

Some additional instructions are provided for the following environments.

For MIT Kerberos

See https://kb.iu.edu/d/aumh:

> ktutil
  ktutil:  addent -password -p username@EXAMPLE.COM -k 1 -e rc4-hmac
  Password for username@EXAMPLE.COM: [enter your password]
  ktutil:  addent -password -p username@EXAMPLE.COM -k 1 -e aes256-cts
  Password for username@EXAMPLE.COM: [enter your password]
  ktutil:  wkt username.keytab
  ktutil:  quit 

For Hiemdal Kerberos

  > ktutil -k username.keytab add -p username@EXAMPLE.COM -e arcfour-hmac-md5 -V 1

If the keytab created in Heimdal does not work, you may need an aes256-cts entry. In this case, locate a machine with MIT Kerberos, and use the MIT Kerberos method instead.

Enable use of Kerberos keytab by Command Line Interface

The 

Steps:

1. Export the following environment variables, where username corresponds to the user ID that is to be used to connect to the platform:

   Code Block
   export KRB5_CLIENT_KTNAME=/path/to/the/username.keytab export GSS_KRB5_NT_PRINCIPAL_NAME=username

2. Invoke the command line interface commands without supplying a password parameter. For more information, see Command Line Interface.

Configure the 

D s platform

for Kerberos

Locate the kerberos section, which controls Kerberos authentication.

Example configuration:

Substitute your own values in place of the example values as appropriate.

"kerberos.enabled": true,
"kerberos.principal": "trifacta",
"kerberos.kdc": "kdc.mssvc.local",
"kerberos.realm": "HADOOPVAL.MSSVC.LOCAL",
"kerberos.keytab": "/opt/trifacta/conf/trifacta.keytab"
"kerberos.principals.hive": "<YOUR_VALUE_HERE><UNUSED>",
"kerberos.principals.namenode": "nn/_HOST@EXAMPLE.COM"
"kerberos.principals.resourcemanager": "<YOUR_VALUE_HERE>",

At this point, you should be able to load files from HDFS and run jobs against the kerberized Hadoop cluster.

Set principal values for YARN

Check the following Hadoop config properties in yarn-site.xml:

principals.jobtracker = yarn.resourcemanager.principal
principals.namenode = dfs.namenode.kerberos.principal