All Products
Search
Document Center

ApsaraMQ for MQTT:AddCustomAuthIdentity

Last Updated:Aug 22, 2024

Adds the information about identity authentication. The identity can be accurate to a client.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
InstanceIdstringYes

The ID of the Message Queue for MQTT instance.

mqtt-cn-xxxx
UsernamestringYes

The username.

test
SecretstringYes

The AccessKey secret.

xxxxx
IdentityTypestringYes

The identity type. Valid values: USER and CLIENT.

USER
ClientIdstringNo

The client ID if you set IdentityType to CLIENT.

GID_test@@@test
SignModestringNo

The signature verification mode. ORIGIN: compares the password and the 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

ParameterTypeDescriptionExample
object

The schema object.

RequestIdstring

The request ID.

020F6A43-19E6-4B6E-B846-44EB31DF****
Codeinteger

The HTTP status code. The status code 200 indicates that the request is successful.

200
Successboolean

Indicates whether the operation is successful. Valid values: true and false.

True
Messagestring

The message returned.

operation success.

Examples

Sample success responses

JSONformat

{
  "RequestId": "020F6A43-19E6-4B6E-B846-44EB31DF****",
  "Code": 200,
  "Success": true,
  "Message": "operation success."
}

Error codes

HTTP status codeError codeError messageDescription
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.-
400Customauth.over.capacityOver custom auth capacity.User-defined permission quantity capacity exceeds the limit
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