Setting Up Big Data Security

Kerberos Authentication versus Secure Impersonation

Kerberos authentication occurs when Pentaho users connect to a Hadoop cluster with a default Kerberos principal. All the Pentaho users connect to the Hadoop cluster with the same Kerberos principal.

In secure impersonation, users connect to the Hadoop cluster as a proxy user. The Pentaho user ID matches the cluster user ID in a one-on-one mapping, and resources are accessed and processes are executed as the cluster user.

Secure impersonation occurs when (1) pre-defined credentials authenticate to a Kerberos server before connecting to the Hadoop cluster, (2) the Pentaho server is configured for secure impersonation, and (3) the Hadoop cluster is secured.

Prerequisites 

For secure impersonation to work, the following conditions must be met:

• The Hadoop cluster must be configured with Kerberos security.
• The Hadoop cluster must have a Kerberos principal that represents Pentaho that can authenticate to the cluster services and have privileges to impersonate.
• Job or transformation requests must come from the Pentaho Server to the cluster to use secure impersonation.
• The Hadoop components must support secure impersonation.

Pentaho support for secure impersonation is determined by whether the Hadoop components support secure impersonation. If the Hadoop component does not support secure impersonation, then Kerberos authentication is used.

The Hadoop administrator is responsible for setting up the cluster users and the Kerberos servers. Refer to the Cloudera documentation for instructions on setting up cluster users. Also see the Apache Hadoop security documentation.

Supported Components*

* These components are currently only supported for secure impersonation on Cloudera 5.7 or greater.

** When running a Pentaho Map Reduce job, you can securely connect to Hive and HBase within the mapper, reducer or combiner.

Secure impersonation directly from the following is not supported:

• PDI client
• Scheduled Jobs and Transformations
• Pentaho Report Designer
• Pentaho Metadata Editor
• Kitchen
• Pan
• Carte.

When you run a transformation or job to run against the cluster from the PDI client, you cannot use secure impersonation. However, if you execute that job or transformation you created in the PDI client from the Pentaho Server, then you can use secure impersonation.

How to Enable Secure Impersonation

Here is how to enable secure impersonation and how the Pentaho Server processes that request. The mapping value simple in the shim configuration file turns on the secure impersonation. See Use Secure Impersonation to Access a Cloudera Cluster for more information on the configuration file for a Cloudera cluster or the Use Secure Impersonation to Access a Hortonworks Cluster for more information on the configuration file for a Hortonworks cluster.

When the Pentaho Server starts, it checks the mapping type value in the configuration file. If the value is disabled or blank, then the server does not use authentication when connecting to the Hadoop cluster. The Pentaho server cannot log onto a secured cluster if the value is set to disabled or blank. If the value is simple, then requests are evaluated for origination from the PDI client tool (Spoon) or from the Pentaho Server. If the request comes from a client tool, then Kerberos authentication is used; if the request comes from the Pentaho Server, then the request is evaluated to see whether the service component supports secure impersonation. If the component does not support secure impersonation, the request uses Kerberos authentication. If the component supports secure impersonation, then the request will use secure impersonation.

When impersonation is successful, the Pentaho Server log will report "Everything looks good! [Hadoop User] is successfully impersonating as [Pentaho User]. "

If you change the mapping type value in the configuration file, you must restart the server for it to take effect.