Permission Governance Process

Updated on 2025-02-18 GMT+08:00

View PDF

Unified permission governance allows you to configure access permissions for the databases, tables, and fields in MRS, DLI, and GaussDB(DWS). It has the following features:

Centralized access control
Permissions of different big data services, such as MRS, DLI, and GaussDB(DWS), are centrally managed. A unified portal is available for you to configure and maintain permissions easily.
Multi-level permission configuration model
Permission models are clearly defined and managed by level. A permission set or role further splits the permission scope defined by the workspace permission set and associates users with permissions for permission control.
Refined permission management
Role-based access control (RBAC) on the console supports refined data permission configuration and permission assignment by role, user, and user group. In addition, on-demand and efficient permission application approval is supported. Approved permissions take effect immediately.
Multi-dimensional permission display
- By workspace member: You can display the data table permissions requested by each user or user group and display, configure, and revoke the permission set relationship of each user or user group.
- By data: You can display and configure the permission relationships of data in the current permission set by database, table, or field.
- By permission: You can display, configure, and revoke the permission policy relationships of data in the current permission set by permission policy.
Workspace resource management
In addition to data permissions, workspace resources, such as data connections and agencies, can be managed.

Use Process

Figure 1 shows the process for using unified permission governance.

Figure 1 Process of using unified permission governance

Unified permission governance supports data permission management, service resource management, and Ranger permission management. Their processes are as follows:

Data permission management process

Authorize dlg_agency.
When using an agency, DataArts Security requires higher cloud service permissions. Before using DataArts Security, you need to grant required permissions to dlg_agency.
Check the cluster version and permissions.
Unified permission governance has requirements on the data connection agent, data source version, and user permissions. Before using it, you need to check and prepare related configurations.
Synchronize IAM users to the data source.
Synchronize user information from IAM to data sources so that users' access to the data sources can be managed based on user information.
Configure workspace permission sets.
As the largest permission set in a DataArts Studio workspace, the workspace permission set defines the resources that can be accessed by users in the workspace.
Configure permission sets.
A permission set associates users with permissions. You can create multiple permission sets to associate users in different scenarios with different permissions. Permissions can be managed through permission synchronization (association of permission sets with roles are more recommended in actual applications.)
Configure common roles.
Create roles in the data source to associate users and permissions. In this way, you can manage permissions more intuitively.
Configure managed roles.
Manage the existing roles in the MRS data source and inherit the MRS data source permissions of the existing roles.
Configure row-level access control.
DataArts Security allows you to view the permissions of workspace members, and manage roles and permission sets.
Synchronize MRS Hive and Hetu permissions.
DataArts Security allows you to view the permissions of workspace members, and manage roles and permission sets.
Apply for permissions.
During access permission management, you can grant permissions to users through permission sets or roles, or apply for permissions and approve permission applications.
Review permission requests.
The approver is the administrator of the permission set or role. The requested permission takes effect immediately after being approved.
Enable fine-grained authentication.
After fine-grained authentication is enabled, data sources no longer use the accounts of the data connections during script execution, job tests, and job scheduling in DataArts Factory of DataArts Studio. Instead, the current user is used for authentication. In this way, different users have different data permissions, and the permissions of roles, permission sets, and queues can be managed.

Service resource management process

Configure queue permissions.
Queue permissions can be used to allocate MRS Yarn and DLI queues to the current workspace and configure queue permission policies for user groups or users.
- After queues are allocated to the workspace, they can be selected during the job node configuration in DataArts Factory.
- After queue permission policies are configured for user groups or users, they have the permissions specified in the policies.
Configure workspace resource permission policies.
DataArts Security supports management of workspace resources, such as data connections and agencies. Unauthorized users cannot view or use the resources.

Ranger permission management process

Configure resource permissions.
You can create permission policies for MRS components and use the Ranger component to manage permissions.
View permission reports.
You can view resource permission policies and their details through a comprehensive permission report.

Data Permission Management

The current data permission control uses the allowlist mechanism, which adds operation conditions to the users to be authorized without affecting the permissions the users already have. If you only want to make the permissions granted by the data permission control take effect, you need to revoke the original permissions of the users to be authorized. By default, DataArts Studio users have the following permissions:

For DLI data sources, the DAYU Administrator or DAYU User has the DLI Service Admin permission by default. Therefore, the users to be authorized have all the data permissions of DLI database tables by default. To remove the default permissions of an authorized user, you need to delete the DLI Service Admin permission of the user.
For GaussDB(DWS) data sources, even if the DAYU Administrator or DAYU User has the GaussDB(DWS) Administrator permission by default, the GaussDB(DWS) database permissions are isolated from the IAM permissions on the console. Therefore, the users to be authorized do not have the data permissions of GaussDB(DWS) database tables by default. Only the data permission granted by the current data permission control takes effect.
For MRS data sources, DAYU Administrator or DAYU User has the MRS Administrator permission by default and will be assigned the corresponding role after it is synchronized to MRS. For details, see Synchronizing IAM Users to MRS. The Ranger component provides the default policy bypass permissions. For details, see Adding a Ranger Permission Policy. If you want to revoke the default permissions of the users to be authorized, perform the following operations to remove the public user group from the default system policies on the Ranger component:
1. Log in to MRS Manager as user admin.
2. On the Manager page, choose Cluster > Services > Ranger. On the Ranger overview page, click RangerAdmin to go to the Ranger WebUI.
  Figure 2 Accessing the Ranger WebUI
3. Log out of the current account and use the Ranger administrator account to log in again. For a common cluster, the admin account for the Manager page can be used as the Ranger administrator account. For a security cluster, rangeradmin is the Ranger administrator account. For details about the default password of rangeradmin, see User Account List.
  Figure 3 Logging out of the current account
4. On the home page, click the component plug-in name in the HADOOP SQL area, for example, Hive.
5. On the Access tab page, locate the default policies whose Groups column contains public (that is, the policy whose value in the Default Policy column is True) and remove the public user group from the policies.
  Figure 4 Policy list

Parent topic: Unified Permission Governance

Previous topic: Unified Permission Governance

Next topic: Authorizing dlg_agency

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot