检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Why Can't I Cancel the Authorization After the IAM User Delegates the Read and Write Permissions on OBS Buckets? The permissions of the IAM user are not clear. As a result, the IAM user may fail to delegate the read and write permissions on OBS buckets to an MPC user.
Creating a User and Granting MPC Permissions This chapter describes how to use IAM to implement fine-grained permissions control for your MPC resources. With IAM, you can: Create IAM users for employees based on your enterprise's organizational structure.
For example, to obtain an IAM token in the CN-Hong Kong region, obtain the endpoint of IAM (iam.ap-southeast-1.myhuaweicloud.com) for this region and the resource-path (/v3/auth/tokens) in the URI of the API used to obtain a user token.
Login Authentication Policy Access Control MPC supports access control through IAM fine-grained authorization policies.
Identity and Access Management (IAM) Create User Groups and Assign Permissions Create IAM Users and Log In Using OBS to store and manage audio and video files Object Storage Service (OBS) Creating a Bucket Uploading an Object
Login Authentication Policy Access Control MPC supports access control through IAM fine-grained authorization policies.
name "password": "********", // IAM user password "domain": { "name": "domainname" // Name of the account to which the IAM user belongs } } } }, "scope
OBS Authorization is not available for IAM users.
The caps on requests are as follows: Single tenants: 100 requests/minute Overall: 1000 requests/minute The region where an IAM API is called must be the same as that where an MPC API is called. Cross-region transcoding is not supported.
Why Can't I Cancel the Authorization After the IAM User Delegates the Read and Write Permissions on OBS Buckets?
OBS authorization is unavailable for IAM users. MPC accesses OBS resources as your role. The transcoded file belongs to you and inherits the bucket policy of the output bucket by default. Procedure Log in to the MPC console.
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.
The region where an IAM API is called must be the same as the region where an MPC API is called.
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.
Request Parameters Table 2 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token 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.
Query Parameters Parameter Mandatory Type Description template_id Yes Integer ID of a custom transcoding template Request Parameters Table 3 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token The token can be obtained by calling the IAM
Table 2 Query Parameters Parameter Mandatory Type Description template_id Yes Integer ID of a watermark template Request Parameters Table 3 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token The token can be obtained by calling the IAM
Table 2 Query Parameters Parameter Mandatory Type Description task_id Yes String Task ID Request Parameters Table 3 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token The token can be obtained by calling the IAM API used to obtain a user
Request Parameters Table 3 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token 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.
Request Parameters Table 3 Request header parameters Parameter Mandatory Type Description X-Auth-Token No String User token 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.