Configuring roles for Cloudera Lakehouse Optimizer users
Ensure that you have the right roles assigned to you before you use Cloudera Lakehouse Optimizer. Depending on you role, you can deploy the Data Hub, create the Cloudera Lakehouse Optimizer policies, and monitor the policies.
To access the Cloudera Lakehouse Optimizer features and REST APIs,
you might require one or more of the following roles:
| Role | Description |
|---|---|
| Cloudera Lakehouse Optimizer-specific roles | |
| Administrators* | Can access and use all the features including all the REST APIs. |
| Operators* | Have limited access to REST APIs. They can run certain tasks, and have no privileges to modify the service configuration. |
| Monitors* | Can only observe the health and status of the service and its running tasks. |
| Other required roles | |
| Privileged CDP User | Can create new groups and assign Cloudera users to those groups, which can then be mapped to Cloudera Lakehouse Optimizer roles in Cloudera Manager. |
| EnvironmentUser | Can access the Lakehouse Optimizer UI. |
| DataHubCreator | Can create the Data Hub. |
| *Ensure that you define the role for the entire environment. This is because you cannot define the role for a specific namespace or table. | |
To assign a role to a user, the Privileged CDP User must perform the following steps:
-
Create the required user groups.
-
Identify and add the users to each group.
-
Synchronize the users for the environment.
-
Map the groups to the Cloudera Lakehouse Optimizer roles.
- Go to the tab.
-
Search for the CLO Security Role Admin property,
remove the default dlm_admin role, and add the
[*** ADMINISTRATOR GROUP NAME ***]. For example,
CLO_Admin. -
Search for the CLO Security Role Operator
property, remove the default dlm_operator role, and
add the [*** OPERATOR GROUP NAME ***]. For example,
CLO_Operator. -
Search for the CLO Security Role Monitor property,
remove the default dlm_monitor role, and add the
[*** MONITOR GROUP NAME ***]. For example,
CLO_Monitor. - Save Changes
