|
|
|
One of the changes that the migration to the ESA corporate authentication system brought to gitlab.esa.int was that you have to set up a Personal Access Token in order to use git+https. |
|
|
\ No newline at end of file |
|
|
|
One of the changes that the migration to the ESA corporate authentication system brought to gitlab.esa.int was that you have to set up a Personal Access Token in order to use git+https.
|
|
|
|
|
|
|
|
A Personal Access Token (PAT) is a password local to Gitlab.
|
|
|
|
|
|
|
|
# Steps to create a PAT
|
|
|
|
1. In the upper-right corner, click your avatar and select Settings.
|
|
|
|
2. On the User Settings menu, select Access Tokens.
|
|
|
|
3. Choose a name and optional expiry date for the token.
|
|
|
|
4. Choose the desired scopes. Normally to work in git from the command-line you will need `read_repository` and `write_repository`.
|
|
|
|
5. Click the Create personal access token button.
|
|
|
|
6. Save the personal access token somewhere safe. Once you leave or refresh the page, you won’t be able to access it again.
|
|
|
|
|
|
|
|
# Stuff to bear in mind
|
|
|
|
- Your username when using a PAT will be the text after the @ when you click in your avatar in the upper-right corner.
|
|
|
|
- The `git` command line tool will probably store your username & PAT in your OS credentials store. If you change your PAT, you will have to reset them `git config --global --unset user.password`
|
|
|
|
- We have a very aggressive rate limit policy. If you input your credentials wrong 5 times in 10 mins you will be banned one hour. |
|
|
\ No newline at end of file |
