Granting or Canceling Authorization for Accessing OBS Buckets

This API is used to grant or cancel authorization for accessing OBS buckets.

For details, see Calling APIs.

PUT /v1/{project_id}/obs/authority

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain the project ID, see Obtaining a Project ID.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	No	String	User token. This parameter is mandatory when token authentication is used. The token 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.
Authorization	No	String	Authentication information. This parameter is mandatory for AK/SK authentication.
X-Sdk-Date	No	String	Time when the request is sent. This parameter is mandatory for AK/SK authentication.
X-Project-Id	No	String	Project ID. This parameter is mandatory for AK/SK authentication.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
bucket	Yes	String	Definition OBS bucket name. Constraints N/A Range N/A Default Value N/A
operation	Yes	Integer	Definition Operation. Constraints N/A Range 1: grants authorization. 0: revokes authorization. Default Value N/A

Status code: 200

Authorization of accessing OBS buckets updated.

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error description.

Modifies the authorization policy of the OBS bucket. The bucket name is video-test02 and the operation is Authorize.

PUT https://{endpoint}/v1/${project_id}/obs/authority

{
  "bucket" : "video-test02",
  "operation" : 1
}

Status code: 400

Update the authorization of accessing OBS buckets failed.

{
  "error_code" : "LIVE.100011001",
  "error_msg" : "Request Illegal"
}

Status Code	Description
200	Authorization of accessing OBS buckets updated.
400	Update the authorization of accessing OBS buckets failed.

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.