Removing Application Group Authorization
Function
Removes specified users from application group authorization. Then, the removed users cannot access the application group. If the operation is repeated, the operation is successful.
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, the following identity policy-based permissions are required.
Action
Access Level
Resource Type (*: required)
Condition Key
Alias
Dependencies
workspace:appGroup:batchDeleteAuthorization
Write
appGroup *
-
-
-
user
-
userGroup
-
URI
POST /v1/{project_id}/app-groups/actions/batch-delete-authorization
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| project_id | Yes | String | Project ID. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| X-Auth-Token | No | String | User token It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
| X-Language | No | String | Language. Options: |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| app_group_ids | Yes | Array of strings | Application group ID. A maximum of 10 application groups can be operated at a time. |
| accounts | Yes | Array of AccountInfo objects | Users or user groups. A maximum of 50 users or user groups can be operated at a time. |
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| id | No | String | User ID or user group ID. The type is determined by account_type. For the user group type, the user group ID is required. USER: user ID USER_GROUP: user group ID |
| account | Yes | String | Username or user group name. The type is determined by account_type. USER: username USER_GROUP: user group name |
| account_type | Yes | String | User type. USER: user USER_GROUP: user group. |
| domain | No | String | Domain name. |
| | No | String | Email. |
| telephone_number | No | String | Mobile phone. |
| platform_type | No | String | Platform type. Options: |
Response Parameters
Status code: 200
Successful.
Status code: 400
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 401
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 403
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 404
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 405
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 500
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Status code: 503
| Parameter | Type | Description |
|---|---|---|
| error_code | String | Error code, which is returned upon failure. |
| error_msg | String | Error message. |
Example Requests
POST /v1/a4da8115c9d8464ead3a38309130523f/app-groups/actions/batch-delete-authorization
{
"app_group_ids" : [ "571784876773081141" ],
"accounts" : [ {
"account" : "user000",
"account_type" : "USER",
"domain" : "wksapp***.huawei.com"
} ]
} Example Responses
None
Status Codes
| Status Code | Description |
|---|---|
| 200 | Successful. |
| 400 | The request cannot be understood by the server due to malformed syntax. |
| 401 | Authentication failed. |
| 403 | Permissions required. |
| 404 | No resources found. |
| 405 | The request method is not allowed. |
| 500 | An internal service error occurred. For details, see the error code description. |
| 503 | Service unavailable. |
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