Configure Hue to use Kerberos

Creating a Kerberos Principal

Set up the Kerberos principal and keytab file .

Using Kerberos Tickets for Hue

Using the keytab and principal you created in the previous step, complete the following steps:

  1. Extract the Kerberos ticket from the keytab file.
  2. Optionally, enable the Kerberos ticket renewer.

Extracting the Kerberos Ticket from the keytab File

To extract the ticket from the keytab file, run the following command (substitute your host and realm for perfnode181.perf.lab@dev-maprtech):

kinit -k -t /opt/mapr/conf/mapr.keytab -c /tmp/hue_krb5_ccache mapr/perfnode181.perf.lab@dev-maprtech

This command extracts the ticket from mapr.keytab and copies it to the path to the Kerberos ticket file used by Hue.

Enabling the Kerberos Ticket Renewer

Kerberos tickets have a default expiration time of 7 days. If you plan to use the Hue Kerberos ticket renewer in your cluster, enable this functionality by making changes to these two files:

  • kdc.conf (add the max_renewable_life parameter)
  • krb5.conf (add the renew_lifetime parameter)

Modifying the hue.ini File

In the kerberos section of the hue.ini file, make the following changes:

  1. Supply the path to Hue's kerberos keytab file.
  2. Supply the kerberos principal name for Hue.
  3. Supply the path to kinit.
  4. Complete the following steps in the [[yarn_clusters]] [[[default]]] section:
    • If you are using a certificate signed by the CA (Certificate Authority), set the ssl_cert_ca_verify value to True.
    • If you are using a self-signed certificate or no certificate, leave the value set to False.
  5. For Hue with secure Hive: In the beeswax section, make sure that the hive_conf_dir property points to a directory containing a valid hive-site.xml file (either the original or a synced copy).
  6. Optional: To enable SSL encryption, see Enable SSL Encryption Between Hue and Hive.

  7. Make sure that you specified a fully-qualified domain name (FQDN) for all services integrated with Hue that uses Kerberos:

    For HttpFS: Set the webhdfs_url property in the [hadoop] [[hdfs_clusters]] [[[default]]] section.

    For HiveServer2: Set the hive_server_host property in the [beeswax] section.

    For Impala: Set the server_host property in the [impala] section.

    For Spark: Set the livy_server_url property in the [impala] section.
    Note: Support for Kerberos integration with Livy was introduced in Hue 4.2.

    For Sqoop2: Set the server_url property in the [sqoop] section.

    For Oozie: Set the oozie_url property in the [liboozie] section.

    For HBase: Set the hbase_clusters property in the [hbase] section.

    For Drill: Refer to section.

The changes are summarized in the following hue.ini files, which you can use as a template:

     # Path to Hue's Kerberos keytab file
     # Kerberos principal name for Hue
     # hue_principal=mapr/<hostname>@<realm>
     # Substitute your hostname and realm in the example below
     # Path to kinit
     # Note that the actual path depends on which Linux OS you are using
  # If Kerberos security is enabled, use fully-qualified domain name
  # (FQDN)
  hive_server_host=<FQDN of Hive Server>
  # Hive configuration directory, where hive-site.xml is located.
  # Change this if your Hive is secured
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY
  # Host of the Impala Server (one of the Impalad)
  server_host=<FQDN of Impalad>
  # Kerberos principal
  # Enter the filesystem uri
  # Use WebHdfs/HttpFs as the communication mechanism.
  # Domain should be the NameNode or HttpFs host.
  # Default port is 14000 for HttpFs.
  webhdfs_url=https://<FQDN of HttpFS>:14000/webhdfs/v1
  # Change this if your HDFS cluster is secured
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY
  # Enter the host on which you are running the ResourceManager
  ## resourcemanager_host=localhost
  # The port where the ResourceManager IPC listens on
  ## resourcemanager_port=8032
  # Whether to submit jobs to this cluster
  # Change this if your YARN cluster is secured
  # URL of the ResourceManager API
  ## resourcemanager_api_url=https://localhost:8090
  # URL of the ProxyServer API
  ## proxy_api_url=https://localhost:8090
  # URL of the HistoryServer API
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY
  # In secure mode (HTTPS), if SSL certificates from Resource Manager's
  # Rest Server have to be verified against certificate authority
  # The Livy Server URL.
  livy_server_url=https://<FQDN of Livy Server>:8998
  # Whether Livy requires client to perform Kerberos authentication.
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY.
  # The URL where the Oozie service runs on. This is required in order for
  # users to submit jobs.
  oozie_url=https://<FQDN of Oozie>:<oozie_port_number>/oozie
  # Requires FQDN in oozie_url if enabled
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY
  # Comma-separated list of HBase Thrift servers for clusters in the format of '(name|host:port)'.
  # Use full hostname with security.
  # If using Kerberos we assume GSSAPI SASL, not PLAIN.
  hbase_clusters=(Cluster|<FQDN of Hbase Thrift Server>:9090)
  # Security mechanism of authentication none/GSSAPI/MAPR-SECURITY
Note: You need to manually set security_enabled property to true and mechanism property to GSSAPI for a Kerberised environment. These options are automatically configured only on a MapR-SASL cluster.

Modifying the core-site.xml File

In the core-site.xml file, provide the shortname for the Kerberos principal as shown. In addition, verify that you configured the proxyuser during configuration. See Configure Hue for details.

<!-- Hue security configuration -->
  <value>*</value> <!-- A group that all users of Hue belong to, or the wildcard value "*" -->

Restarting Warden and Hue

After you make all the changes to the files listed above, restart Warden and Hue so the changes will take effect.