Configuring an HTTPS Password
Introduction
An HTTPS password is a user credential used for pulling and pushing code using the HTTPS protocol. 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.
You can configure HTTPS passwords by referring to Setting the HTTPS Password for the First Timeor Configuring HTTPS Passwords in Best Practices.
Constraints
Item |
Description |
---|---|
Permission |
|
Password format |
An HTTPS password consists of two parts:
|
File size |
The size of a single file to be pushed using HTTPS cannot exceed 200 MB. If you need to transfer a file larger than 200 MB, configure an SSH key by referring to Configuring an SSH Key and use the SSH key to transfer the file. |
Setting the HTTPS Password for the First Time
By default, the HTTPS password is your IAM 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 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 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.
- Verify whether the HTTPS password takes effect by referring to Verifying Whether Your HTTPS Password Takes Effect. If the HTTPS password does not take effect, rectify the fault by referring to Related Document.
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 Password. Click Change, enter the old password, new password, and confirm it. Click Save. A dialog box is displayed, indicating that the password is set successfully.
You can also click Reset. You need to bind an email address for the first-time password reset. Set Verification Code, New Password, and Confirm Password, and click Save. 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
). Use HTTPS to clone again, and enter the correct account and password in the dialog box that is displayed. - Verify whether the HTTPS password takes effect by referring to Verifying Whether Your HTTPS Password Takes Effect. If the HTTPS password does not take effect, rectify the fault by referring to Related Document.
Verifying Whether Your HTTPS Password Takes Effect
After setting the HTTPS password, you can run the following command in Git Bash to clone the repository that you have permission to access:
git clone https://username:password@exaple.com/repo_path.git
- username is the configured HTTPS username.
- password is the configured HTTPS password..
- example.com/repo_path.git is the HTTPS address of the repository to be cloned.
If the code is successfully cloned with the command, the HTTPS password has been successfully set.
As shown in the following figure, the repository Test_Repo is successfully cloned to the local host.
Figure 1 Cloned repository
Related Document
- You can configure HTTPS passwords by referring to Configuring HTTPS Passwords in Best Practices.
- 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot