Updates the information about custom identity authentication.
Debugging
Authorization information
There is currently no authorization information disclosed in the API.
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
InstanceId | string | Yes | The ID of the ApsaraMQ for MQTT instance. | post-111**** |
Username | string | Yes | The username. | test |
Secret | string | Yes | The AccessKey secret. | xxxx |
IdentityType | string | Yes | The identity type. Valid values:
| USER |
ClientId | string | No | The client ID if you set IdentityType to CLIENT. | GID_test@@@test |
SignMode | string | Yes | The signature verification mode. ORIGIN: compares the password and AccessKey secret. SIGNED: uses the HMAC_SHA1 algorithm to sign the client ID to obtain a password and then compares the password. | SIGNED |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "3F00084A-7F07-4B15-BADA-8903A4FB****",
"Code": 200,
"Success": true,
"Message": "operation success."
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | InstancePermissionCheckFailed | An error occurred while validating the permissions of the instance. Please verify the account that created the instance and its permissions settings. |
400 | InvalidParameter.%s | An error occurred while validating the parameter. The parameter may be missing or invalid. |
404 | ApiNotSupport | The specified API is not supported. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|
No change history