Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Configuring Resource Permissions

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

This section describes how to create resource permission policies for Ranger to control access to MRS resources and reduce data security risks for your enterprise.

Prerequisites

  • A Ranger connection has been created in Management Center, and a correct RangerAdmin service IP address and Ranger service port have been set for the connection (see MRS Ranger Connection Parameters for details).
    NOTE:

    When you test the Ranger connection in Management Center, the Ranger service IP address and port will not be verified, and no error will be reported even if they are incorrect. You are advised to check them manually.

  • Ranger authentication has been enabled for the corresponding MRS cluster. In security mode, Ranger authentication is enabled by default. In common mode, Ranger authentication is disabled by default. For details, see Enabling Ranger Authentication.

Constraints

  • Resource permission policies depend on the Ranger authentication of MRS clusters. Currently, only permissions on MRS resources can be controlled.
  • A permission policy takes effect about 1 minute after being configured.

MRS Components that Support Access Control and the Permission List

Ranger can be used to integrate components in MRS clusters of version 3.0.0 or a later version to enable fine-grained access permission control for components. Table 1 lists the supported components and describes related permissions. For details, see Configuring Component Permission Policies.

Table 1 Supported components and permissions

Component

Permission

HDFS

HDFS file permissions:

  • Read: the permission required for read
  • Write: the permission required for write
  • Execute: the permission required for executing a job

Hive

Hive database, data table, and column permissions:

  • Select: the permission required for query
  • Update: the permission required for update
  • Create: the permission required for creation
  • Drop: the permission required for dropping
  • Alter: the permission required for alteration
  • All: the permissions required for all operations
  • Temporary UDF Admin: the permission required for managing a temporary UDF

Yarn

Yarn queue permissions:

  • submit-app: the permission required for submitting a queue
  • admin-queue: the permission required for managing a queue

HBase

HBase column and column family permissions:

  • Read: the permission required for read
  • Write: the permission required for write
  • Create: the permission required for creation
  • Admin: the permission required by an administrator

Kafka

Kafka topic permissions:

  • Publish: the permission required for production
  • Consume: the permission required for consumption
  • Configure: the permission required for expanding the capacity of a topic
  • Describe: the permission required for query
  • Create: the permission required for creating a topic
  • Delete: the permission required for deleting a topic
  • Describe Configs: the permission required for querying configurations
  • Alter Configs: the permission required for modifying configurations

Storm

Storm topology permissions:

  • Submit Topology: the permission required for submitting a topology
  • File Upload: the permission required for uploading a file
  • File Download: the permission required for downloading a file
  • Kill Topology: the permission required for deleting a topology
  • Rebalance: the permission required for rebalance
  • Activate: the permission required for activation
  • Deactivate: the permission required for deactivation
  • Get Topology Conf: the permission required for getting the configurations of a topology
  • Get Topology: the permission required for getting a topology
  • Get User Topology: the permission required for getting a user topology
  • Get Topology Info: the permission required for getting the information of a topology
  • Upload New Credential: the permission required for uploading a new credential

Creating an HDFS Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 1 Resource Permission Settings page

  3. Click Configure to the right of hacluster under the HDFS component, and click Create in the upper part of the page displayed.

    Figure 2 Creating a permission policy

  4. Set the parameters and click OK.

    Figure 3 Assigning a permission policy
    Table 2 Parameters for configuring an HDFS permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    When you need to create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Topology

    HDFS path for access permission control.

    Recursion

    If the function is enabled, the resource path is in recursive mode. If the function is disabled, the resource path is in non-recursive mode. Policy Status is set to Enabled by default.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Block all other accesses

    If you select Block all other accesses, only specified users or user groups are allowed to access the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

Creating a Hive Access Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 4 Resource Permission Settings page

  3. Click Configure to the right of the Hive component, and click Create in the upper part of the page displayed.

    Figure 5 Creating a permission policy

  4. Set the parameters and click OK.

    Figure 6 Configuring a Hive policy
    The following table lists the parameters of a Hive permission policy.
    Table 3 Parameters of a Hive permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    database

    The database parameter is mandatory. You can set the database whose permissions need to be controlled. Fuzzy search is supported.

    table

    The table parameter is mandatory. You can set the table whose permissions need to be controlled. Fuzzy search is supported.

    Column

    The Column parameter is mandatory. You can set the column whose permissions need to be controlled. Fuzzy search is supported.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Block all other accesses

    If you select Block all other accesses, only specified users or user groups are allowed to access the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

Creating a Hive Masking Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 7 Resource Permission Settings page

  3. Click Configure to the right of the Hive component, and click Create in the upper part of the Mask tab page.

    Figure 8 Creating a permission policy

  4. Set the parameters and click OK.

    Figure 9 Configuring a Hive policy
    Table 4 Parameters of a Hive permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Database

    The Database parameter is mandatory. You can set the database whose permissions need to be controlled. Fuzzy search is supported.

    Data Table

    The Data Table parameter is mandatory. You can set the table whose permissions need to be controlled. Fuzzy search is supported.

    Column

    The Column parameter is mandatory. You can set the column whose permissions need to be controlled. Fuzzy search is supported.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Mask

    The masking mode for users or user groups to access data.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Mask Mode: Columns that require permission control in a Hive table are masked based on the value of this parameter.

Creating a Hive Row-Level Filter Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 10 Resource Permission Settings page

  3. Click Configure to the right of the Hive component, and click Create in the upper part of the Row-level Filter tab page.

    Figure 11 Creating a Hive row-level filter policy

  4. Set the parameters and click OK.

    Figure 12 Configuring a Hive policy
    Table 5 Parameters of a Hive permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Database

    The Database parameter is mandatory. You can set the database whose permissions need to be controlled. Fuzzy search is supported.

    Data Table

    The Data Table parameter is mandatory. You can set the table whose permissions need to be controlled. Fuzzy search is supported.

    Column

    The Column parameter is mandatory. You can set the column whose permissions need to be controlled. Fuzzy search is supported.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Row-level Filter

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Row-level Filter: Filter by field content. The parameter format is as follows: Field=Value. Example: state=1.

Creating an HBase Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 13 Resource Permission Settings page

  3. Click Configure to the right of the HBase component, and click Create in the upper part of the page displayed.

    Figure 14 Creating an HBase permission policy

  4. Set the parameters and click OK.

    Figure 15 Configuring an HBase policy
    Table 6 Parameters of an HBase permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Data Table

    The Data Table parameter is mandatory. You can set the table whose permissions need to be controlled. Fuzzy search is supported.

    Column

    The Column parameter is mandatory. You can set the column whose permissions need to be controlled. Fuzzy search is supported.

    Column Family

    Column Family is mandatory. This parameter indicates a set of column families in an HBase cluster.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Block all other accesses

    If you select Block all other accesses, only specified users or user groups are allowed to access the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

Creating a Yarn Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 16 Resource Permission Settings page

  3. Click Configure to the right of the Yarn component, and click Create in the upper part of the page that is displayed.

    Figure 17 Creating a Yarn permission policy

  4. Set the parameters and click OK.

    Figure 18 Configuring a Yarn policy
    Table 7 Parameters of a Yarn permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Queue

    Resource scheduling queue in the Yarn service.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Block all other accesses

    If you select Block all other accesses, only specified users or user groups are allowed to access the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

Creating a Kafka Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 19 Resource Permission Settings page

  3. Click Configure to the right of the Kafka component, and click Create in the upper part of the page that is displayed.

    Figure 20 Creating a Kafka permission policy

  4. Set the parameters and click OK.

    Figure 21 Configuring a Kafka policy
    Table 8 Parameters of a Kafka permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Policy Conditions

    Range of IP addresses that can access the Kafka topic.

    Topic

    The message topic of a Kafka cluster.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Policy Conditions: the range of IP addresses that can access the Kafka topic.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Policy Conditions: the range of IP addresses that can access the Kafka topic.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

Creating a Storm Permission Policy

  1. On the DataArts Studio console, locate a workspace and click DataArts Security.
  2. Choose Access Permission Management > Resource Permission Settings from the left navigation bar.

    NOTE:

    If error message "cluster [mrs_3x_autotest_do_not_del] get service failed. due to [null response from cdm:[404 NOT FOUND]]." is displayed, check whether the RangerAdmin service IP address and Ranger service port of the Ranger connection are correct in Management Center by referring to MRS Ranger Connection Parameters.

    Figure 22 Resource Permission Settings page

  3. Click Configure to the right of the Storm component, and click Create in the upper part of the page displayed.

    Figure 23 Creating a Storm permission policy

  4. Set the parameters and click OK.

    Figure 24 Configuring a Storm policy
    Table 9 Parameters of a Storm permission policy

    Parameter

    Description

    Policy Type

    The policy type is automatically generated based on the selected service component. Policy Type can be set to Access, Mask, and Row-level Filter. Mask and Row-level Filter are specific to Hive.

    Policy Status

    If Policy Status is Enabled, the permission policy takes effect immediately. If Policy Status is Disabled, the permission policy does not take effect after being created. Policy Status is set to Enabled by default.

    Overwrite

    If Overwrite is set to Enabled, the new policy takes effect and the old policy does not take effect. Overwrite is set to Enabled by default.

    To create a temporary access policy, enable Overwrite and set Validity Period as required. In this way, even if the temporary access policy expires, the original permission policy still takes effect.

    Audit Log

    If Audit Log is set to Enabled, logs are recorded. The log content includes the client access time, client IP address, client user, and resource operation result.

    Policy Name

    Policy name is mandatory. A policy name can include only letters, numbers, underscores (_), and hyphens (-). Up to 50 characters are allowed.

    Description

    A description of the policy. Up to 256 characters are allowed.

    Topology

    Tasks in a Storm cluster.

    Validity Period

    You can set the effective time and expiration time of a policy. You can configure multiple time ranges.

    Allowed

    Users and user groups that are allowed to access the resources.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

    Exceptions

    If you select Exceptions for Allowed, users who are not allowed to access the system are added to the user group that is allowed to access the system.

    If you select Exceptions for blocked, users who are allowed to access the system are added to the user group that is blocked from the system.

    Block all other accesses

    If you select Block all other accesses, only specified users or user groups are allowed to access the system.

    Blocked

    Blocked is displayed when Block all other accesses is not selected. Users and user groups that are not allowed to access the system can be specified in the Blocked area.

    • Username: MRS user.
    • Role: MRS role.
    • Group: MRS user groups.
    • Permission: the permission required by users who are not allowed to access the system. Permission and Username can be left blank or not left blank at the same time. For details on service permissions, see Table 1.
    • Granted: If Granted is selected, management permissions are assigned to appropriate users and groups. Delegated administrators can update and delete policies and create sub-policies based on the original policies.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback