Configure Kerberos Authentication for Sqoop2

As of Sqoop2 1.99.6-1507, you can configure Sqoop2 to use Kerberos authentication. However, the cluster and other components that work with Sqoop2, such as Hue, must also use Kerberos authentication. Note the following items when you complete the configuration steps:
  • Replace <FQDN> with the FQDN of the server. To determine this value, run hostname -f in the command line.
  • Replace <REALM> with the realm name in the krb5.conf file, which is generated when you install the KDC server on the cluster.
Configuring Kerberos Authentication for Sqoop2:
  1. Using the kadmin program, run the following commands to create principals for Sqoop 2: Kerberos uses the principal HTTP/<FQDN>@<REALM> for communication between Sqoop2 client and Sqoop2 server. The principal mapr/<FQDN>@<REALM> is the Sqoop2 user that communicates between Sqoop2 server and MapR-FS.
    addprinc -randkey HTTP/<FQDN>@<REALM>
    addprinc -randkey mapr/<FQDN>@<REALM>
  2. Using the kadmin program, run the following commands to create keytabs for the principals:
    xst -k /opt/mapr/conf/mapr.keytab HTTP/<FQDN>@<REALM> 
    xst -k /opt/mapr/conf/mapr.keytab mapr/<FQDN>@<REALM>
  3. Modify the following properties in Sqoop2 configuration file (/opt/mapr/sqoop/sqoop-<version>/server/conf/<FQDN>@<REALM><FQDN>@<REALM>*
  4. Start Sqoop2 server.
    maprcli node services -name sqoop2 -action start -nodes <space delimited list of nodes>
  5. Using the kinit program, run the following command to generate a ticket:
    kinit HTTP/<FQDN>@<REALM> -kt /opt/mapr/conf/mapr.keytab 
  6. Start the Sqoop2 client.
    sudo -u mapr /opt/mapr/sqoop/sqoop-<version>/bin/ client