All Products
Search
Document Center

ApsaraMQ for MQTT:UpdateCustomAuthPermission

更新時間:Oct 30, 2024
This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Updates the permissions on a topic.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

ID of the Cloud Message Queue MQTT version instance.

post-cn-0pp12gl****
IdentityTypestringYes

The identity type. Valid values:

  • USER
  • CLIENT
USER
IdentitystringYes

Username or Client ID.

test
PermitActionstringYes

The permissions that you want to grant.

Enumeration Value:
  • PUB
  • SUB
  • PUB_SUB
PUB_SUB
EffectstringYes

Specifies whether to allow or deny access.

Enumeration Value:
  • ALLOW
  • DENY
ALLOW
TopicstringYes

Authorized Topic, supporting multi-level MQTT topics and wildcards.

test/t1

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

RequestIdstring

Id of the request

8CC04203-679B-4DED-89D9-E7C2E979****
Codeinteger

Error code returned upon failed invocation. For more information, see Error Codes.

200
Successboolean

Indicates whether the call was successful. true: Call succeeded. false: Call failed.

True
Messagestring

Information

operation success.

Examples

Sample success responses

JSONformat

{
  "RequestId": "8CC04203-679B-4DED-89D9-E7C2E979****",
  "Code": 200,
  "Success": true,
  "Message": "operation success."
}

Error codes

HTTP status codeError codeError message
400InstancePermissionCheckFailedAn error occurred while validating the permissions of the instance. Please verify the account that created the instance and its permissions settings.
400InvalidParameter.%sAn error occurred while validating the parameter. The parameter may be missing or invalid.
404ApiNotSupportThe specified API is not supported.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history