Cloudera Manager User Roles

Access to Cloudera Manager features is controlled by user accounts that specify an authentication mechanism and one or more user roles. User roles determine the Cloudera Manager capabilities that an authenticated user can perform and the features visible to the user in the Cloudera Manager Admin Console. Privileges for specific clusters determine on which clusters the user roles for a user apply to.

Documentation for Cloudera Manager administration and management tasks indicate user roles required to perform the task.

Displaying Your Roles

To view your roles, perform the following step:

  1. In the Cloudera Manager Admin Console, select <username> > My Profile .

Default User Roles

By default, Cloudera Manager ships with user roles that have privileges for all clusters that Cloudera Manager manages. You can create roles that are a combination of a default user role and privileges on a specific cluster. For more information about this type of role, see User Roles with Privileges for a Cluster.

The following list describes the actions each user role can perform:
  • Auditor
    • View configuration and monitoring information in Cloudera Manager.
    • View audit events.
  • Read-Only
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • View events and logs.
    • View replication jobs and snapshot policies.
    • View YARN applications and Impala queries.
    The Read-Only role does not allow the user to:
    • Add services or take any actions that affect the state of the cluster.
    • Use the HDFS file browser.
    • Use the HBase table browser.
    • Use the Solr Collection Statistics browser.
  • Dashboard
    • Create, edit, or remove dashboards that belong to the user.
    • Add an existing chart or create a new chart to add to a dashboard that belongs to the user.
    • Perform the same actions as the Read-Only role.
  • Limited Operator
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • Decommission hosts (except hosts running Cloudera Management Service roles).
    • Perform the same actions as the Read-Only role.

    The Limited Operator role does not allow the user to add services or take any other actions that affect the state of the cluster.

  • Operator
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • Stop, start, and restart clusters, services (except the Cloudera Management Service), and roles.
    • Decommission and recommission hosts (except hosts running Cloudera Management Service roles).
    • Decommission and recommission roles (except Cloudera Management Service roles).
    • Start, stop, and restart KMS.
    • Perform the same actions as the Read-Only role.

    The Operator role does not allow the user to add services, roles, or hosts, or take any other actions that affect the state of the cluster.

  • Configurator
    • View configuration and monitoring information in Cloudera Manager.
    • Perform all Operator operations.
    • Configure services (except the Cloudera Management Service).
    • Enter and exit maintenance mode.
    • Manage dashboards (including Cloudera Management Service dashboards).
    • Start, stop, and restart KMS
    • Perform the same actions as the Read-Only role.
  • Cluster Administrator - View all data and perform all actions except the following:
    • Administer Cloudera Navigator.
    • View replication schedules and snapshot policies.
    • View audit events.
    • Manage user accounts and configuration of external authentication.
    • Manage Full Administrator accounts.
    • Configure HDFS encryption, administer Key Trustee Server, and manage encryption keys.
    • Use the HDFS file browser, the HBase table browser, and the Solr Collection browser.
    • View the Directory Usage Report
    • View the HBase Statistics Page
    • Perform the same actions as the Read-Only role.
  • BDR Administrator
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • Perform replication and define snapshot operations.
    • Use the HDFS file browser, the HBase table browser, and the Solr Collection browser.
    • View the Directory Usage Report
    • View the HBase Table Statistics Page
    • Perform the same actions as the Read-Only role.
  • Navigator Administrator
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • Administer Cloudera Navigator.
    • View audit events.
    • Use the HDFS file browser, the HBase table browser, and the Solr Collection browser.
    • Perform the same actions as the Read-Only role.
  • User Administrator
    • View configuration and monitoring information in Cloudera Manager.
    • View service and monitoring information.
    • Manage user accounts and configuration of external authentication.
    • Use the HDFS file browser, the HBase table browser, and the Solr Collection browser.
    • Perform the same actions as the Read-Only role.
  • Key Administrator
    • View configuration and monitoring information in Cloudera Manager.
    • Configure HDFS encryption, administer Key Trustee Server, and manage encryption keys.
    • Start, stop, and restart KMS
    • Use the HDFS file browser, the HBase table browser, and the Solr Collection browser.
    • Perform the same actions as the Read-Only role.
  • Full Administrator - Full Administrators have permissions to view all data and do all actions on all cluster.

User Roles with Privileges for a Cluster

In addition to the default user roles, you can create user roles that apply only to specific clusters. Creating this new role is done by assigning a privilege for a specific cluster to a default role. When a user account has multiple roles, the privileges are the union of all the roles.

For example, the user account milton has the Limited Operator role and Read-Only role with a scope of Cluster 1. Additionally, milton has the Configurator role on Cluster 2.

On Cluster 1, milton can perform all the actions that a Limited Operator and Read-Only can.

On Cluster 2, milton can perform all the actions that a Configurator can.

The user account milton cannot perform these or any other actions on the other clusters that are managed by Cloudera Manager because the account does not have any other roles.

Another user account, edith, has the Configurator role with privileges for all clusters. This means that edith can perform the actions of the Configurator role on all clusters that Cloudera Manager manages since the scope is all clusters.

You can assign privileges for a specific cluster to the following user roles:

  • Cluster Administrator
  • Configurator
  • Limited Operator
  • Operator
  • Read-Only

User roles that cannot be assigned privileges for a specific cluster apply to all clusters. For example, if edith has the Key Administrator user role, she can perform the actions of a Key Administrator on all clusters.

Cluster-Specific Permissions

Adding a User Role for a Specific Cluster

To create a role that has privileges for a specific cluster, perform the following steps:

  1. In the Cloudera Manager Admin Console, navigate to Administration > Users & Roles > Roles.
  2. Click Add Role.
  3. Specify the following:
    • Privilege: The user role and cluster you want to assign privileges for.
    • Users: The users you want to assign to this new role. You can assign users now or at a later time.
    • LDAP Group/External Program Exit Codes/SAML Attributes/SAML Script Exit Codes: The external mapping you want to assign this new role to. You can assign external mappings now or at a later time with the process described in Mapping External Authentication to a Role.

      This field is based on your authentication mode and does not appear for local users.

      Valid values for the External Program Exit Code and SAML Script Exit Code are between 0 and 127. You defined what users you want to associate with theses values when you configure your external authentication. For more information,

      If you are upgrading to Cloudera Manager 6 from Cloudera Manager 5, existing mappings are imported from Cloudera Manager 5. These imported mappings can be changed.

      If you are upgrading to Cloudera Manager 6 from Cloudera Manager 5, existing mappings are imported from Cloudera Manager 5. These imported mappings can be changed.

      The following list describes the LDAP groups imported from Cloudera Manager 5:
      • LDAP Full Administrator Groups
      • LDAP User Administrator Groups
      • LDAP Cluster Administrator Groups
      • LDAP BDR Administrator Groups
      • LDAP Configurator Groups
      • LDAP Key Administrator Groups
      • LDAP Navigator Administrator Groups
      • LDAP Operator Groups
      • LDAP Limited Operator Groups
      • LDAP Auditor Groups
      The following list describes the SAML and External Program codes imported from Cloudera Manager 5:
      • 0 - Full Administrator
      • 1 - Read-Only
      • 2 - Limited Operator
      • 3 - Operator
      • 4 - Configurator
      • 5 - Cluster Administrator
      • 6 - BDR Administrator
      • 7 - Navigator Administrator
      • 8 - User Administrator
      • 9 - Auditor
      • 10 - Key Administrator
  4. Click Add.

Mapping External Authentication to a Role

If you are using an external authentication, such as a SAML Script, you must map its information to Cloudera Manager user roles. Before you can map a role though, make sure that it exists. If it does not exist, create it by completing the steps described in Adding a User Role for a Specific Cluster.

For example, you are using a SAML Script and want to assign user accounts that correspond with exit code 15 to a Cluster Administrator role with privileges for a cluster named cluster1.

To accomplish this, perform the following steps in the Cloudera Manager Admin Console:

  1. Navigate to Administration > Users & Roles > Roles.
  2. Based on your authentication method, select LDAP Groups, SAML Attributes, SAML Scripts, or External Programs.
  3. Click Add <authentication method> Mapping.
  4. Fill in the value for your authentication method, such as SAML Script Exit Code, and select the role you want to map to that value from the dropdown menu.

    For SAML Scripts and External Programs, valid values are between 0 and 127.

  5. Click Save.
  6. Repeat this process for all the roles you want to map.

If you are upgrading to Cloudera Manager 6 from Cloudera Manager 5, existing mappings are imported from Cloudera Manager 5. These imported mappings can be changed.

The following list describes the LDAP groups imported from Cloudera Manager 5:
  • LDAP Full Administrator Groups
  • LDAP User Administrator Groups
  • LDAP Cluster Administrator Groups
  • LDAP BDR Administrator Groups
  • LDAP Configurator Groups
  • LDAP Key Administrator Groups
  • LDAP Navigator Administrator Groups
  • LDAP Operator Groups
  • LDAP Limited Operator Groups
  • LDAP Auditor Groups
The following list describes the SAML and External Program codes imported from Cloudera Manager 5:
  • 0 - Full Administrator
  • 1 - Read-Only
  • 2 - Limited Operator
  • 3 - Operator
  • 4 - Configurator
  • 5 - Cluster Administrator
  • 6 - BDR Administrator
  • 7 - Navigator Administrator
  • 8 - User Administrator
  • 9 - Auditor
  • 10 - Key Administrator

Assigning Users to a Role

In addition to mapping groups, such as LDAP groups, to a user role, you can also assign individual users to a user role. If you do not assign a role, the local user defaults to no access. This means that the user cannot perform any actions on the cluster.

To add a user account to a role, perform the following steps:

  1. In the Cloudera Manager Admin Console, navigate to Administration > Users & Roles > Roles.
  2. Click Assign for the role you want to modify.
  3. Specify the Users or <Authentication Method Value> groups you want to assign to the role.
  4. Save the changes.

Removing a User or External Mapping from a User Role

Perform the following steps to remove a user account or external mapping from a user role:

  1. In the Cloudera Manager Admin Console, navigate to Administration > Users & Roles > Roles.
  2. Click Assign for the role you want to modify.
  3. Click the X for each user or external mapping you want to remove from the user role and click Save.

Removing a Role

To remove a role with a specific privilege, you must first remove all the user accounts that have that role. Note that you cannot remove the default roles that Cloudera Manager ships with.

The following steps describe how to remove users and then delete the role:
  1. In the Cloudera Manager Admin Console, navigate to Administration > Users & Roles > Roles.
  2. Click Assign for the role you want to modify.
  3. Click the X for each user or external mapping you want to remove from the user role and click Save.
  4. Click Remove.

Removing the Full Administrator User Role

Minimum Required Role: User Administrator (also provided by Full Administrator)

In some organizations, security policies may prohibit the use of the Full Administrator role. The Full Administrator role is created during Cloudera Manager installation, but you can remove it as long as you have at least one remaining user account with User Administrator privileges.

To remove the Full Administrator user role, perform the following steps.

  1. Add at least one user account with User Administrator privileges, or ensure that at least one such user account already exists.
  2. Ensure that there is only a single user account with Full Administrator privileges.
  3. While logged in as the single remaining Full Administrator user, select your own user account and either delete it or assign it a new user role.
A consequence of removing the Full Administrator role is that some tasks may require collaboration between two or more users with different user roles. For example:
  • If the machine that the Cloudera Navigator roles are running on needs to be replaced, the Cluster Administrator will want to move all the roles running on that machine to a different machine. The Cluster Administrator can move any non-Navigator roles by deleting and re-adding them, but would need a Navigator Administrator to perform the stop, delete, add, and start actions for the Cloudera Navigator roles.
  • In order to take HDFS snapshots, snapshots must be enabled on the cluster by a Cluster Administrator, but the snapshots themselves must be taken by a BDR Administrator.