|
|
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.
|
|
|
You have to set up a Personal Access Token in order to use git+https, since gitlab.esa.int is using the ESA Corporate Authentication System and we do not store your passwords.
|
|
|
|
|
|
A Personal Access Token (PAT) is a password local to Gitlab. **Your ESAAD password will not work**. You need to create a PAT to fetch the code from the command-line or other tools like TortoiseGit or Visual Studio.
|
|
|
|
|
|
# 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.
|
... | ... | @@ -10,6 +13,10 @@ A Personal Access Token (PAT) is a password local to Gitlab. **Your ESAAD passwo |
|
|
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 secure store system. So it is possible that you will only need to input it once.
|
... | ... | |