MapR 5.1 is at End of Life (EOL) and no longer supported. Please see the latest documentation. This documentation is not being updated.

Home
5.1 Administration
This section contains administration information such as managing your cluster, data, users, jobs and security information such as configuring your security environment and auditing.
Security Guide
Getting Started with MapR Security
Describes the two core scenarios that allow quick implementation of security features.
Enable Impersonation
Enable Impersonation for HBase

MapR 5.1 Documentation

5.1 Administration
This section contains administration information such as managing your cluster, data, users, jobs and security information such as configuring your security environment and auditing.
- Administrator Guide
- Security Guide
  - Security Overview
    Describes the security features of the MapR Converged Data Platform.
  - Security Architecture
    Describes the default security architecture and additional authentication and encryption capabilities.
  - Logging into a Secure Cluster
    Describes how to use tickets to access a secure MapR cluster.
  - Tickets and Certificates
    Describes how tickets and certificates authenticate users and servers to a cluster.
  - Getting Started with MapR Security
    Describes the two core scenarios that allow quick implementation of security features.
  - Configuring MapR Security
    Describes how to enable security features and configure the components on a secure cluster.
  - Auditing of Cluster Administration and Operations on Directories, Files, Tables, and Streams
    Describes how to process and use audit records to improve data analysis.

Enable Impersonation for HBase

About this task

HBase can be configured to offer impersonation, with or without Kerberos. This means that users can send commands to HBase through Hue without losing the fact that they will be run under their own credentials, instead of the 'hue' user.

Procedure

Make sure you have the following in your hbase-site.xml file:

<property>
  <name>hbase.thrift.support.proxyuser</name>
  <value>true</value>
</property>
  
<property>
  <name>hbase.regionserver.thrift.http</name>
  <value>true</value>
</property>

Check in core-site.xml that HBase is authorized to impersonates someone.

<property>
  <name>hadoop.proxyuser.hbase.hosts</name>
  <value>*</value>
</property>
  
<property>
  <name>hadoop.proxyuser.hbase.groups</name>
  <value>*</value>
</property>

Check that Hue points to a local config directory of HBase specified in its hue.ini file:
```
[hbase]
hbase_conf_dir=/etc/hbase/conf
```