Modifying User Permission Groups in Batches
Function
Modifies user permission groups in batches.
Debugging
You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.
Authorization Information
Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.
- If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
- If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.
URI
POST /v2/{project_id}/desktops/change-user-privilege-group
Parameter | Mandatory | Type | Description |
|---|---|---|---|
project_id | Yes | String | Project ID. |
Request Parameters
Parameter | Mandatory | Type | Description |
|---|---|---|---|
desktops | Yes | Array of ChangeUserPrivilegeGroupDesktopInfo objects | Desktop information list. |
user_privilege_group | No | String | User permission group to which the desktop user belongs. Desktop users who are not contained in the parameter desktops will belong to this permission group. |
Parameter | Mandatory | Type | Description |
|---|---|---|---|
desktop_id | Yes | String | ID of the desktop to be modified. |
attach_user_infos | No | Array of ChangeUserPrivilegeGroupUserInfo objects | Information about the user whose permission group is to be modified. If this parameter is not transferred for a desktop, the parameter user_privilege_group of the upper-layer application structure is used as the permission group of the user. |
Parameter | Mandatory | Type | Description |
|---|---|---|---|
user_name | Yes | String | Name of the object assigned with a desktop. If type is set to USER, enter the username. If type is set to GROUP, enter the user group name. |
domain | No | String | Domain to which the user belongs. |
user_privilege_group | No | String | User group to which the desktop user belongs. |
type | Yes | String | Object type. Options: |
Response Parameters
Status code: 200
Parameter | Type | Description |
|---|---|---|
job_id | String | Task ID. |
Status code: 400
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Status code: 401
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Status code: 403
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Status code: 404
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Status code: 409
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Status code: 500
Parameter | Type | Description |
|---|---|---|
error_code | String | Error code, which is returned upon failure. |
error_msg | String | Error message. |
error_detail | String | Error details. |
encoded_authorization_message | String | Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason. |
Example Requests
{
"desktops" : [ {
"desktop_id" : "string",
"attach_user_infos" : [ {
"user_name" : "string",
"user_privilege_group" : "string",
"type" : "user"
} ]
} ]
} Example Responses
Status code: 200
Normal.
{
"job_id" : "string"
} Status Codes
Status Code | Description |
|---|---|
200 | Normal. |
400 | The request cannot be understood by the server due to malformed syntax. |
401 | Authentication failed. |
403 | No operation permissions. |
404 | No resources found. |
409 | Operation conflict. |
500 | An internal service error occurred. For details about the error code, see the error code description. |
Error Codes
See Error Codes.
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
