Actions Supported by Policy-based Authorization
This topic describes the actions supported by OMS in role/policy-based authorization.
Supported Actions
SMS provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:
- Permissions: statements in a policy that allow or deny certain operations.
- APIs: REST APIs that can be called by a user who has been granted specific permissions.
- Actions: specific operations that are allowed or denied.
- Related actions: actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the related actions.
- IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. "√" indicates that the action supports the project and "×" indicates that the action does not support the project. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management
OMS supports the following actions in custom policies:
|
Permission |
API |
Action |
IAM Project |
|---|---|---|---|
|
Updating migration tasks in batches |
POST /v2/{project_id}/tasks/batch-update |
oms:task:update |
√ |
|
Listing migration tasks |
GET /v2/{project_id}/tasks |
oms:task:list |
√ |
|
Creating a migration task |
POST /v2/{project_id}/tasks |
oms:task:create |
√ |
|
Querying a migration task |
GET /v2/{project_id}/tasks/{task_id} |
oms:task:get |
√ |
|
Deleting a migration task |
DELETE /v2/{project_id}/tasks/{task_id} |
oms:task:delete |
√ |
|
Pausing a migration task |
POST /v2/{project_id}/tasks/{task_id}/stop |
oms:task:update |
√ |
|
Starting a migration task |
POST /v2/{project_id}/tasks/{task_id}/start |
oms:task:update |
√ |
|
Modifying the traffic limiting rules of a migration task |
PUT /v2/{project_id}/tasks/{task_id}/bandwidth-policy |
oms:task:update |
√ |
|
Listing synchronization tasks |
GET /v2/{project_id}/sync-tasks |
oms:synctask:list |
√ |
|
Creating a synchronization task |
POST /v2/{project_id}/sync-tasks |
oms:synctask:create |
√ |
|
Querying a synchronization task |
GET /v2/{project_id}/sync-tasks/{sync_task_id} |
oms:synctask:get |
√ |
|
Deleting a synchronization task |
DELETE /v2/{project_id}/sync-tasks/{sync_task_id} |
oms:synctask:delete |
√ |
|
Querying statistics about a synchronization task |
GET /v2/{project_id}/sync-tasks/{sync_task_id}/statistics |
oms:synctask:statistics |
√ |
|
Pausing a synchronization task |
POST /v2/{project_id}/sync-tasks/{sync_task_id}/stop |
oms:synctask:update |
√ |
|
Starting a paused synchronization task |
POST /v2/{project_id}/sync-tasks/{sync_task_id}/start |
oms:synctask:update |
√ |
|
Creating a synchronization event for a synchronization task |
POST /v2/{project_id}/sync-tasks/{sync_task_id}/events |
oms:synctask:createEvent |
√ |
|
Creating a migration task group |
POST /v2/{project_id}/taskgroups |
oms:taskgroup:create |
√ |
|
Listing migration task groups |
GET /v2/{project_id}/taskgroups |
oms:taskgroup:list |
√ |
|
Querying details about a migration task group |
GET /v2/{project_id}/taskgroups/{group_id} |
oms:taskgroup:get |
√ |
|
Deleting a migration task group |
DELETE /v2/{project_id}/taskgroups/{group_id} |
oms:taskgroup:delete |
√ |
|
Pausing a migration task group |
PUT /v2/{project_id}/taskgroups/{group_id}/stop |
oms:taskgroup:update |
√ |
|
Restarting a migration task group |
PUT /v2/{project_id}/taskgroups/{group_id}/start |
oms:taskgroup:update |
√ |
|
Retrying a failed migration task group |
PUT /v2/{project_id}/taskgroups/{group_id}/retry |
oms:taskgroup:update |
√ |
|
Updating a migration task group |
PUT /v2/{project_id}/taskgroups/{group_id}/update |
oms:taskgroup:update |
√ |
|
Listing objects in a bucket |
POST /v2/{project_id}/objectstorage/buckets/objects |
oms::listObjects |
√ |
|
Checking whether data in a source bucket can be obtained from CDN |
POST /v2/{project_id}/objectstorage/buckets/cdn-info |
oms::checkCdnInfo |
√ |
|
Listing all buckets |
POST /v2/{project_id}/objectstorage/buckets |
oms::listBuckets |
√ |
|
Querying the region of a bucket |
POST /v2/{project_id}/objectstorage/buckets/regions |
oms::listBucketRegions |
√ |
|
Checking whether a bucket has objects with a specified prefix |
POST /v2/{project_id}/objectstorage/buckets/prefix |
oms::checkBucketPrefix |
√ |
|
Querying regions supported for a cloud vendor |
GET /v2/{project_id}/objectstorage/data-center |
oms::listCloudRegions |
√ |
|
Querying supported cloud vendors |
GET /v2/{project_id}/objectstorage/cloud-type |
oms::listCloudTypes |
√ |
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