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 Ecosystem
This guide contains a section for each open source project that MapR supports. You can learn how to install, configure, use, and integrate each project within the context of a MapR cluster.
Sentry
Integrating Sentry
Integrate Sentry with other ecosystem components to enable those components to use Sentry authorization. You can also integrate Sentry with Hue in order to use the Hue Security application to manage Sentry privileges and roles.

MapR 5.1 Documentation

5.1 Ecosystem
This guide contains a section for each open source project that MapR supports. You can learn how to install, configure, use, and integrate each project within the context of a MapR cluster.
- AsyncHBase
- Cascading
- Drill
- Flume
- HBase
- HCatalog
- Hive
- HttpFS
- Hue
- Impala
- Mahout
- Myriad
- Oozie
- Pig
- OpenStack Sahara (Mitaka)
- Sentry
  - Sentry Feature Support
  - Installing Sentry
    You can install Sentry using the MapR installer or with manual steps.
  - Upgrading Sentry
    Complete the following steps to upgrade manually. If you installed Sentry with the MapR Installer, use the latest version of the MapR Installer to perform the upgrade.
  - Configuring Sentry
    The steps to configure Sentry are determined by the storage model, the type of security used by the cluster, and the components that will use Sentry authorization.
  - Integrating Sentry
    Integrate Sentry with other ecosystem components to enable those components to use Sentry authorization. You can also integrate Sentry with Hue in order to use the Hue Security application to manage Sentry privileges and roles.
    - Configuring Impala to Use Sentry Authorization
      You can configure Impala to work with Sentry for authorization. When you configure Sentry authorization for Impala, Impala uses operating system IDs to associate privileges with each user that runs the impala-shell or client program.
    - Configure Sqoop2 to use Sentry Authorization
      As of Sentry 1.6.0, you can configure Sqoop2 to use Sentry authentication when Sentry uses the database storage model, the cluster is secure , and the cluster uses Kerberos authentication.
    - Configure Hive to use Sentry Authorization
      Configure Hive to use Sentry when you want to use Sentry authorization with Impala.
    - Integrate Hue with Sentry
      As of Sentry 1.6, you can integrate Hue with Sentry on a secure cluster that uses kerberos authentication but the integration is not supported on a secure cluster that uses MapR-SASL authentication. Integrate Hue with Sentry when you want to use the Hue Security application to manage Sentry roles and privileges. When you integrate Hue with Sentry, Sentry must use the database storage model.
- Spark
- Sqoop
- Storm
- Third Party Solutions

Integrating Sentry

Integrate Sentry with other ecosystem components to enable those components to use Sentry authorization. You can also integrate Sentry with Hue in order to use the Hue Security application to manage Sentry privileges and roles.

You can configure Sentry to provide authorization in the following scenarios:

Sentry Version	Sentry Storage Mode	Component Integration	Cluster Security
1.6.0	Database	Impala 2.2.0/2.5.0 and Hive 1.2.1	Insecure cluster Secure cluster with Kerberos authentication
1.6.0	Database	Sqoop2	Secure cluster with Kerberos authentication
1.6.0	File-Based	Impala 2.2.0/2.5.0 and Hive 1.2.1	Insecure cluster Secure cluster with Kerberos authentication
1.4.0	File-Based	Impala 1.4.1 and Hive 0.13	Insecure cluster Secure cluster without Kerberos authentication for Hive

NOTE:

When you configure Impala to use Sentry authorization, Impala and Hive both must use Sentry for authentication. Also, impersonation cannot be enabled for Hive.
For clusters with Hive but not Impala, authorization can be implemented using Hive’s native authorization mechanisms;Sentry is not needed.