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 Flume

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 Flume

The mapr user is the only user with impersonation enabled on a MapR cluster. Flume agents that use impersonation must run as the user mapr on the cluster. To use impersonation with Flume, your flume.conf file must contain the properties in the following example, with the correct values for your cluster:

Property	Value	Comment
agent1.sinks.sink1.type	HDFS
agent1.sinks.sink1.hdfs.proxyUser	user ID of target user	Can be any valid MapR user identity.
agent1.sinks.sink1.hdfs.kerberosPrincipal	mapr
agent1.sinks.sink1.hdfs.kerberosKeytab	path to file	If you are not using Kerberos to authenticate, this can be any valid file. If you are using Kerberos to authenticate, provide the path to your `flume.keytab` file.

Even though in this instance Flume is not using Kerberos authentication, the values for the hdfs.kerberosPrincipal and hdfs.kerberosKeytab parameters must exist in flume.conf. The user component of the principal must be the username of the user running flume-ng. The file at the location specified by hdfs.kerberosKeytab must exist, but need not be a valid keytab if Kerberos is not being used.