Configuring an Access Token
Introduction
Access tokens can keep your code resources secure. When you authorize a third party to access your repository, you can create an access token and set its validity period to avoid exposing your account and password. You can view the Constraints and configure access tokens by referring to Configuring an Access Token.
Constraints
|
Item |
Description |
|---|---|
|
Number of access tokens |
A maximum of 20 tokens can be created for CodeArts Repo. |
|
Validity period |
One month by default. Max. one year. You can set the validity period of an access token as needed. |
|
Single-time visibility |
Configuring an Access Token
|
Parameter |
Description |
|---|---|
|
Token Name |
Custom name with a maximum of 200 characters. |
|
Description |
Optional. If the description is empty, -- will be displayed in the list. Max. 200 characters. |
|
Permissions |
This parameter is selected by default and cannot be modified. Read/Write repo: Read from and write into repositories using HTTPS. |
|
Expires |
Time when a token expires. The default expiration date is set to 30 days from the current date, including the current day. For example, if a token is created on July 3, the default expiration date will be 23:59:59 on August 2. The expiration date can be set to one year from the creation date and cannot be left empty. |
Related Document
After configuring the token, you can run the following command to clone the repository to the local host:
git clone https://private-token:Your Token@example.com/repo_path.git
- Your Token is the copied token.
- If the HTTPS clone address of the repository is https://example.com/repo_path.com, the content following https:// is example.com/repo_path.git.
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
