Configuring HTTPS Password

Updated on 2024-12-12 GMT+08:00

View PDF

When you push code to or pull code from CodeArts Repo, the repository verifies your identity and permissions. HTTPS password is an identity authentication mode for remote access to CodeArts Repo. You only need to set this once.

HTTPS username
It consists of your tenant name and IAM username: Tenant name/IAM username.
HTTPS password
8 to 32 characters with at least three types of the following characters: digits, uppercase letters, lowercase letters, and special characters, and cannot be the same as the username of the HTTPS password or the reverse-order username.

Setting the HTTPS Password for the First Time

By default, the HTTPS password is your login password which can be synced in real time. You can also perform the following steps to set the initial password.

Go to the repo list page of CodeArts Repo, click the nickname in the upper right corner, and choose This Account Settings > Repo > HTTPS Password.

You can also go to the repo list page and click Set HTTPS Password in the upper right corner.
Click Reset to go to the password resetting page if you are setting the password for the first time. Click Set new password, fill in the Password and Confirm Password, and click OK. A dialog box is displayed, indicating that the password is set successfully.
Regenerate the repository credential locally and check the IP address whitelist when the new password is created. Otherwise, you cannot use CodeArts Repo repositories.

Delete the local credential (for example, on Windows, choose Control Panel > User Accounts > Manage Windows Credentials > Generic Credentials). Use HTTPS to clone again, and enter the correct account and password in the dialog box that is displayed.
Check whether the HTTPS password takes effect by referring to Verifying Whether Your HTTPS Password Takes Effect.

NOTE:

If your account is upgraded to a HUAWEI ID, the tenant-level function of Use Huawei Cloud login password is no longer supported (the function is still valid for IAM users).
Federated users cannot be bound to email addresses and do not support the HTTPS protocol.
If the message " SSL certificate problem" is displayed when you perform step 3, run the git config --global http.sslVerify false command on the Git client to disable the SSL verification function of Git.

Changing the HTTPS Password

Go to the repo list page of CodeArts Repo, click the alias in the upper right corner, and choose This Account Settings > Repo > HTTPS Password.

You can also go to the repo list page and click Set HTTPS Password in the upper right corner.
Click Set new password. The page for resetting the password is displayed. Click Change, fill in Old Password, New Password, and Confirm Password, and click OK. A dialog box is displayed, indicating that the password is set successfully.

You can also click Reset. You need to bind an email address if you are setting the password for the first time. Set Verification Code, New Password, and Confirm Password, and click Save. A dialog box is displayed, indicating that the password is set successfully.
Check whether the HTTPS password takes effect by referring to Verifying Whether Your HTTPS Password Takes Effect.

NOTE:

If the message "No backend available: service IAM" is displayed when you bind an email address, contact your administrator to bind an email address for you, return to the HTTPS password resetting page, and refresh it.

Verifying Whether Your HTTPS Password Takes Effect

After setting the HTTPS password, you can run the git clone https://username:password@example.com/repo_path.git command in Git Bash to clone the code repository to which you have access. Username indicates the HTTPS username, Password indicates the HTTPS password, and example.com/repo_path.git indicates the HTTPS address of the code repository to be cloned. If the code is successfully cloned with the command, the HTTPS password has been successfully set.

Parent topic: Environment and Personal Settings

Previous topic: Configuring an SSH Private Key

Next topic: Configuring an Access Token

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

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

Chatbot