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 Drill
Enable Drill Impersonation without Hive

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 Drill Impersonation without Hive

About this task

Chaining is a system-wide setting that applies to all views. Currently, Drill does not provide an option to allow different chain lengths for different views. Complete the following steps on each Drillbit node to enable user impersonation, and set the maximum number of chained user hops that Drill allows:

Procedure

Navigate to <drill_installation_directory>/conf/ and edit drill-override.conf file.

Under drill.exe, add the following:

drill.exec.impersonation: {
      enabled: true,
       max_chained_user_hops: 3
}

Verify that enabled is set to 'true'.
Set the maximum number of chained user hops that you want Drill to allow.

Add the following line to the drill-env.sh file:

export MAPR_TICKETFILE_LOCATION=/opt/mapr/conf/mapruserticket

Restart the Drillbit process on each Drill node.
```
<DRILLINSTALL_HOME>/bin/drillbit.sh restart
```