This section describes how to ensure that the  is configured correctly to connect to Hive when Ranger is enabled for Hive.  Ranger provides role-based authorization for Hive and other Hadoop components on the Hortonworks platform. 

Ranger effectively functions as a whitelist of URI's; by default, access is denied for any object in Hive. When a URI is requested, Ranger checks HDFS for permissions for the authenticated user. If HDFS denies access, then Ranger checks its defined set of URI's for the permission and, if a match is found, grants access for the authenticated user.


Before you begin, please verify that your enterprise has deployed both Hive and Ranger according to recommended configuration practices. For more information, please consult the documentation that was provided with your Hadoop distribution.

NOTE: Before you begin, you must integrate the with Hive. See Configure for Hive.

Secure Impersonation with  and Hive with Ranger

Secure impersonation ensures consistent and easily traceable security access to the data stored within your Hadoop cluster.  

NOTE: Although not required, secure impersonation is highly recommended for connecting the platform with Hive.

Since secure impersonation for the combination of Hive Server 2 and Ranger is not supported by Ranger, you must apply the following additional configuration changes to the  to enable secure impersonation in the environment:  

  1. Enable the platform with secure impersonation.  See Configure for secure impersonation for details.
  2. Add the hive service user hive to the Unix or LDAP group
  3. Set the following parameter:

    "hdfs.permissions.userUmask" = 027
  4. Ensure that the Unix or LDAP group has read access to the Hive warehouse directory, as described in the following section. For more information, see

Users and Groups for Ranger

When the  is enabled with secure impersonation and submits requests to Hive, the following steps occur:

  1. The platform authenticates as the user through Kerberos.
  2. The Hive server authorizes access to the underlying table through Ranger as the Hadoop principal user assigned to .  

    NOTE: This Hadoop principal is the user that should be configured through policies in Ranger to have the appropriate privileges. 


  3. The Hive server executes access to the physical data file on HDFS as the Unix user  hive, which should be part of the group .

NOTE: Since Ranger assigns access to databases, tables, and columns to Unix users and groups, a common practice is to assign the Hadoop principal users (used by ) to dedicated Unix groups that are separate from the Unix group use within Ranger. Ranger should not grant any privileges and roles to the Unix group .

NOTE: In UNIX environments, usernames and group names are case-sensitive. Please verify that you are using the case-sensitive names for users and groups in your Hadoop configuration and .

Policies in Ranger

In Ranger, you can configure access through policies. A Ranger policy is a combination of:

  • Specified database, table, or tabled column
  • Permissions associated with that specified object.
  • Assignment of permissions to individual users or groups

Required Permissions

NOTE: In general, to manage access through Ranger, permissions to underlying Hadoop components such as HDFS or Hive should be minimized within those components. All permissions in Ranger are additive, which means that you should be careful about overlapping users and groups.

The following components require these permissions at a minimum to be assigned to the Hadoop principal:

HDFSRead, Write, Execute

Select, Update.

Create (for Hive publishing)

Verify Operations

After you have completed your configuration changes, you should restart the platform. See Start and Stop the Platform.

To verify platform operations, run a simple job. For more information, see Verify Operations.