This is critical and I hope there is a debug method. We had this working back in January but something has happened and this is an absolute showstopper as I have developers who are trying to get going with Git and GitLab (company's chosen repository software) and I cannot get them authenticated.
#Authentication failed sourcetree gitlab password#
Credentials are fixed at PAT and logging in with the GitLab account name and the PAT as password produces "Authentication failed." in the dialog box. I create the account on Sourcetree under Tools > Opetions > Authentication > Add.įields selected are "GitLab EE", the site URL, protocol HTTPS. I have generated the PAT with api, read_user. I am reasonably certain since I can use another client and PAT authentication, that the trouble is Sourcetree.
GitKraken works fine with the PAT, and I can log in over browser to GitLab EE. Using Sourcetree version 3.3.4 I am having massive issues with getting the client to authenticate with GitLab EE. Then in the edit hosting account dialog choose gitlab and https as protocol and then click on refresh personal access token button.Īfter that in the username and password dialog enter your gitlab username and paste that token you copied it before as your password. Once you leave or refresh the page, you won’t be able to access it again. Save the personal access token somewhere safe.Click the Create personal access token button.Choose a name and optional expiry date for the token.
On the User Settings menu, select Access Tokens.In the upper-right corner, click your avatar and select Settings.You can create as many personal access tokens as you like from your GitLab profile.
0 kommentar(er)
