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
Configuring MapR Security
Describes how to enable security features and configure the components on a secure cluster.
Secured TaskTracker
Describes how to control user access to TaskTracker.

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.
    - Enabling and Disabling Security Features on Your Cluster
      Describes how to enable and disable wire-level security on the nodes of your cluster.
    - Configuring Impersonation
      Describes how to use impersonation to centralize control over user actions.
    - Running Commands on Remote Secure Clusters
      Describes how to manage multiple secure clusters from one secure cluster.
    - Adding Cross-Cluster Tickets to Secure Clusters
      Describes how to add cross-cluster tickets to secure clusters that push and pull data.
    - PAM Configuration
      Describes how to use PAM to verify passwords.
    - Secured TaskTracker
      Describes how to control user access to TaskTracker.
    - Access Control Lists
      Describes how to create different types of ACLs.
    - Access Control Expressions
      Describes how to use ACEs to control user permissions for MapR-DB tables.
    - Permissions
      Describes requirements for API user permissions and file permissions.
    - Securing Open Source Components
      Describes how to use JAAS to configure security for open source components.
    - Configuring Kerberos User Authentication
      Describes how to configure Kerberos for the CLDB.
    - Mirror Volumes and Secure Clusters
      Describes how to configure security for the source and destination clusters of a mirror.
    - Configuring a MapR Cluster to Access a HDFS Cluster
      Describes how to create a connection between a MapR cluster and an HDFS 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.

Secured TaskTracker

Describes how to control user access to TaskTracker.

About this task

You can control which users are able to submit jobs to the TaskTracker. By default, the TaskTracker is secured; all TaskTracker nodes should have the same user and group databases, and only users who are present on all TaskTracker nodes (same user ID on all nodes) can submit jobs. You can disallow certain users (including root or other superusers) from submitting jobs, or remove user restrictions from the TaskTracker completely.

NOTE: You must restart the TaskTracker after changing a node's hostname.

Disallowing Root

Procedure

Edit mapred-site.xml (MapReduce v1) and set mapred.tasktracker.task-controller.config.overwrite = false on all TaskTracker nodes.
Edit taskcontroller.cfg and set min.user.id=0 on all TaskTracker nodes.
Restart all TaskTrackers.

Disallowing All Superusers

Procedure

Edit mapred-site.xml (MapReduce v1) and set mapred.tasktracker.task-controller.config.overwrite = false on all TaskTracker nodes.
Edit taskcontroller.cfg and set min.user.id=1000 on all TaskTracker nodes.
Restart all TaskTrackers.

Disallowing Specific Users

Procedure

Edit mapred-site.xml (MapReduce v1) and set mapred.tasktracker.task-controller.config.overwrite = false on all TaskTracker nodes.
Edit taskcontroller.cfg and add the parameter banned.users on all TaskTracker nodes, setting it to a comma-separated list of usernames. Example:
```
banned.users=foo,bar
```
Restart all TaskTrackers.

Removing All User Restrictions and Running All Jobs as Root

Procedure

Edit mapred-site.xml (MapReduce v1) and set mapred.task.tracker.task-controller = org.apache.hadoop.mapred.DefaultTaskController on all TaskTracker nodes.
Restart all TaskTrackers.

NOTE: When you make the above setting, all jobs submitted by any user will run as root, and will have the ability to overwrite, delete, or damage data regardless of ownership or permissions.