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.
PAM Configuration
Describes how to use PAM to verify passwords.

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.
      - Configuring PAM for REST API
        Describes how to configure the JPAM login for REST API.
      - Configuring PAM to Use LDAP
        Describes the verifications and installation steps needed to configure PAM to use LDAP.
      - Configuring PAM to Use Kerberos
        Describes how to install the packages and configure the Kerberos client to use PAM.
      - Creating a Custom mapr-admin Profile for PAM
        Describes how to install the packages and configure the Kerberos client to use PAM.
    - 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.

PAM Configuration

Describes how to use PAM to verify passwords.

MapR uses Pluggable Authentication Modules (PAM) for password verification in a variety of places. Make sure PAM is installed and configured on the node running the mapr-webserver, or other components that will use PAM to verify passwords.

There are typically several PAM modules (profiles), configurable via configuration files in the /etc/pam.d/ directory. Any component verifying user passwords tries the following three profiles in order:

sudo (/etc/pam.d/sudo)
sshd (/etc/pam.d/sshd)
mapr-admin (If you have created the /etc/pam.d/mapr-admin profile and the component checks beyond the first two profiles.)

The profile configuration file (for example, /etc/pam.d/sudo) should contain an entry corresponding to the authentication scheme used by your system. For example, if you are using the simplest form of local OS authentication, check for an entry similar to the following - consult with your Unix system administrator if you are uncertain:

auth    sufficient      pam_unix.so  # For local OS Auth

Component-Specific PAM Configurations

Some ecosystem components have unique requirements that require setup of a component-specific PAM configuration. See the Ecosystem Guide for the component.