Help Center/ Cloud Certificate & Manager/ Private Certificate Authority (PCA) User Guide/ Using IAM to Grant Access to PCA/ Using IAM Roles or Policies to Grant Access to PCA
Updated on 2026-07-31 GMT+08:00
View PDF
Share

Using IAM Roles or Policies to Grant Access to PCA

This chapter describes how to use IAM to implement fine-grained permissions control of roles and policies for your PCA resources. With IAM, you can:

  • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing PCA resources.
  • Grant only the permissions required for users to perform a task.
  • Entrust a Huawei Cloud account or cloud service to perform professional and efficient O&M on your PCA resources.

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

This section describes how to assign permissions based on roles and policies. Figure 1 shows the authorization process.

Prerequisites

Before assigning permissions to a user group, you need to understand the PCA permissions. For details, see Role and Policy Permission Management. For details about the permissions that can be granted to other services, see System-defined Permissions.

Process Flow

Figure 1 Process for granting PCA permissions
  1. Create a user group and assign permissions.

    Create a user group on the IAM console and grant the user group the PCA FullAccess.

  2. Create a user and add it to a user group.

    On the IAM console, create an IAM user and add it to the user group created in 1.

  3. Log in and verify permissions.

    Log in to the CCM console by using the created user, and verify that the user only has read permissions for CCM.

    Choose Cloud Certificate Management Service under Security in the Service List. If no message appears indicating that you have no permissions to access the service, the policy PCA FullAccess has already taken effect.

Example Custom Policies

Custom policies can be created to supplement the system-defined policies of PCA. Add actions in custom policies as needed. For details about supported actions, see Actions Supported by Policy-based Authorization.

You can create custom policies in either of the following ways:

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
  • JSON: Edit JSON policies from scratch or based on an existing policy.

For details, see Creating a Custom Policy. The following lists examples of common PCA custom policies.

  • Example 1: authorizing users to create a CA 
    {
        "Version": "1.1",
        "Statement": [
                {
                        "Action": [
                                "pca:ca:create
                        ],
                        "Effect": "Allow"
                }
        ]
}
  • Example 2: denying certificate deletion

    A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    If you need to assign permissions of the PCA FullAccess policy to a user but you want to prevent the user from deleting certificates, you can create a custom policy for denying certificate deletion, and attach both policies to the group that the user belongs to. Then, the user can perform all operations on certificates except deleting certificates. The following is an example of a deny policy:

    {
        "Version": "1.1",
        "Statement": [
                {
                        "Action": [
                                "pca:ca:delete"
                        ],
                        "Effect": "Deny"
                }
        ]
}