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 resources.

With IAM, you can use your 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.

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

Enhanced Hyperledger Fabric

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 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 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 1 System-defined roles and policies supported by enhanced Hyperledger Fabric

Role/Policy Name	Description	Type	Dependency
BCS Administrator	BCS administrator	System-defined role	Tenant Guest, Server Administrator, ELB Administrator, CCE Cluster Admin, SFS Administrator, SWR Admin, APM FullAccess, AOM FullAccess, CCE Administrator, VPC Administrator, EVS Administrator, ECS FullAccess, DMS Administrator, and BSS Administrator
BCS FullAccess	Full permissions for BCS	System-defined policy	None
BCS ReadOnlyAccess	Read-only permissions for BCS	System-defined policy	None

If you select BCS FullAccess, you need to set namespace permissions for the CCE cluster because BCS depends on CCE and the CCE namespace uses Kubernetes RBAC authorization. See Permissions Management to set namespace permissions. Suggestion: Create a cluster in CCE, grant the cluster-admin permission to the user groups/users in the cluster. Then, go to the BCS console, create a BCS instance. On the Configure Resources page, select Use an existing CCE cluster for Cluster.