Actions Supported by Identity Policy-based Authorization
IAM provides system-defined identity policies to define typical cloud service permissions. You can also create custom identity policies using the actions supported by cloud services for more refined access control.
In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.
SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.
To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.
This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.
- For details about how to use these elements to edit an IAM custom identity policy, see Creating a Custom Identity Policy.
- For details about how to use these elements to edit a custom SCP, see Creating an SCP.
Actions
Actions are specific operations that are allowed or denied in an identity policy.
- The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
- The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by CodeArts TestPlan, see Resources.
- The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by CodeArts TestPlan, see Table 3.
- The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.
| Action | Description | Access Level | Resource Type (*: required) | Condition Key | Alias |
|---|---|---|---|---|---|
| codeartstestplan:testSuite:create | Grant permission to create test suit. | Write | - | - | |
| codeartstestplan:variable:get | Grant permission to get variable. | Read | - | - | |
| codeartstestplan:testCase:create | Grant permission to create test case. | Write | - | - | |
| codeartstestplan:testPlan:get | Grant permission to get test plan. | Read | - | - | |
| codeartstestplan:testPlan:create | Grant permission to create test plan. | Write | - | - | |
| codeartstestplan:testPlan:list | Grant permission to create test plan list. | List | - | - | |
| codeartstestplan:testSuite:get | Grant permission to get test suit. | Read | - | - |
| API | Action | Dependencies |
|---|---|---|
| codeartstestplan:testSuite:create | - | |
| codeartstestplan:variable:get | - | |
| POST /v1/projects/{project_id}/plans/{plan_id}/testcases/batch-add | codeartstestplan:testCase:create | - |
| codeartstestplan:testPlan:get | - | |
| codeartstestplan:testPlan:get | - | |
| codeartstestplan:testPlan:create | - | |
| codeartstestplan:testPlan:get | - | |
| codeartstestplan:testPlan:list | - | |
| POST /v4/{project_id}/tasks/{task_uri}/testcases/batch-query | codeartstestplan:testSuite:get | - |
Resources
CodeArts TestPlan does not support resource-level authorization. To allow access to CodeArts TestPlan, use a wildcard (*) in the Resource element of the identity policy, indicating that the identity policy will be applied to all resources.
Conditions
CodeArts TestPlan does not support service-specific condition keys in identity policies.It can only use global condition keys applicable to all services. For details, see Global Condition Keys.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
