A MapR Expansion Pack (MEP) provides a set of ecosystem components that work together on one or more MapR cluster versions.
Only one version of each ecosystem component is available in each MEP. For example, only one version of Hive and one version
of Spark is supported in a MEP.

You can configure user impersonation and isolation on a secure cluster that uses Kerberos authentication. Configure
user impersonation for Storm when you want the mapr user to submit jobs on behalf of another user. After you enable user impersonation for Storm, you can also configure
isolation to submit a job as a user other than the mapr user.

You can configure Storm to use a multi-tenant scheduler. Configure a multi-tenant scheduler when you want to isolate
topologies from one another.The multi-tenant scheduler also provides the ability to limit the total resources that
user can consume in the cluster.

This topic provides links to the locations of MapR's public APIs. These APIs are available for application development
purposes.

Configure Kerberos for Storm

You can configure Storm to use Kerberos authentication on a secure
cluster.

Complete the basic storm configurations before you configure Storm to use Kerberos
authentication. For details on the basic Storm configuration, see Configure Basic Storm Parameters

When you complete the following steps to configure Kerberos authentication, replace
instances of <fqdn>@<realm> and <fqdn> with data that is specific to your
environment. These steps must be performed on each node in the Storm cluster.

Note: When Storm runs on more than one node in the cluster, the
storm.auth.simple-acl.admins and
storm.auth.simple-acl.users must specify values that
are node-specific. For example, if you are configuring these properties on a
node that runs the Nimbus service, the node name and users must correspond
to the hostname of the Nimbus node and users available on that Nimbus node.