Verifying HTTPS Account and Password (Deprecated)

This API is used to check whether the username and password entered when you upload or download code using HTTPS are valid.

This API has been deprecated. Use the API in Verifying HTTPS Account and Password instead.

POST /v1/user/{iam_user_uuid}/validateHttpsInfo

**Table 1** Path parameters
Parameter	Mandatory	Type	Description
iam_user_uuid	Yes	String	Explanation: iamId Range: 32 digits and letters.

**Table 2** Request header parameter
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	Explanation: User token. It can be obtained by calling the corresponding IAM API. The value of X-Subject-Token in the response header is the user token. Constraints: Mandatory Range: 1–100,000 characters. Default value: None

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
pwd	Yes	String	Explanation: HTTPS password Constraints: 8–32 characters. The password must contain at least three types of the following characters: digits, uppercase letters, lowercase letters, and special characters. It cannot be the same as the username or the username spelled backwards.

Status code: 200

**Table 4** Response body parameters
Parameter	Type	Description
error	Error object	Explanation: Response error. Range: None
result	String	Explanation: Response result. Range: verificationPassed: The password is correct.
status	String	Explanation: Response status of the API. Range: success: The API call is successful. failed: The API call failed.

**Table 5** Error
Parameter	Type	Description
code	String	Explanation: Error code returned when the API fails to be called. Range: CH.080002 CH.010112 CH.010008
message	String	Explanation: Error code returned when the API fails to be called. Range: Incorrect password format. User not found. Invalid password.

POST https://{endpoint}/v1/user/{iam_user_uuid}/validateHttpsInfo

{
  "pwd" : "XXX"
}

Status code: 200

{
  "result" : "verificationPassed",
  "status" : "success"
}

Status Code	Description
200	OK

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

For any further questions, feel free to contact us through the chatbot.