Help Center> Blockchain Service> Service Overview> Permissions Management

Permissions Management

If you need to assign different permissions to employees in your enterprise to access your BCS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your Huawei Cloud resources.

With IAM, you can use your Huawei Cloud account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use BCS resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using BCS resources. For details about permission management and configuration, see Permissions Management for enhanced Hyperledger Fabric and Huawei Blockchain Permissions Management for HBS.

If your Huawei Cloud account does not require individual IAM users for permissions management, skip this section.

IAM is free of charge. You pay only for the resources you use.

BCS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

BCS is a project-level service deployed and accessed in specific physical regions. To assign BCS permissions to a user group, specify the scope as region-specific projects, for example, cn-north-1 for CN North-Beijing1 and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. Switch to a region where you have been authorized to access BCS.

Table 1 lists the system-defined policy supported by enhanced Hyperledger Fabric.

Table 2 lists the system-defined policy supported by HBS.

Table 1 System-defined roles and policies supported by enhanced Hyperledger Fabric

Role/Policy Name

Description

Type

Dependency

BCS Administrator

Full permissions for BCS

System-defined role

Tenant Guest, Server Administrator, ELB Administrator, SFS Administrator, SWR Admin, APM FullAccess, AOM FullAccess, CCE Administrator, VPC Administrator, and EVS Administrator

Table 2 System-defined roles and policies supported by HBS

Role/Policy Name

Description

Type

BCS Administrator

Full permissions for BCS

System-defined role

Tenant Administrator

Administrator permissions for all cloud services (except IAM)

System-defined role

Enhanced Hyperledger Fabric and HBS blockchains do not support fine-grained authorization.