MapR allows you to implement a completely custom configuration of security for components within a secure MapR installation. However, about 80% of secure MapR installations actually implement one of two core scenarios.
For reasons driven by dependencies between security options selected for different MapR ecosystem components, these two options are defined in terms of the extent to which you wish to use, or avoid use of Kerberos. If your security plans fit within one of these scenarios, you can implement the component settings described without having to do all the planning to work out the dependencies between security option choices made for different components.
To quickly implement security in a secured MapR cluster, configure security settings for a scenario in which Kerberos is used wherever it is supported: