I've successfully added my GitHub account on Sourcetree.
Next is GitLab. On the Edit Hosting Account, I clicked the Refresh Personal Access Token button. A dialog would appear, asking my GitLab username & password. I entered the correct input, and the result was "Failed to check login for user ". Now I'm confused.
I'm on 64-bit Windows 10, BTW.
GitLab REST API only works with Personal Access Tokens https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
The UI uses a shared component to gather the password/token hence the wording, but we will review that.
I have the same problem... using sourcetree 3.1.2 and trying to connect in remote repository GitLab Community Edition 8.7.0...
I tried using my userID and my password... tried using my userID and PAT... tried using username in blank and PAT... no success...
I make a success test connecting to Gitlab API using SoapUI and PAT... so the API is working, the problems seems to be in sourcetree.
When try to connect o got "Authentication failed" message...
Anyone how to solve it?
I had this problem but i solved it.
According to this url https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html :
You can create as many personal access tokens as you like from your GitLab profile.
Enter Sourcetree as Token Name
Read step 7 again. you have to copy your token somewhere. it's something like this:
Then in the edit hosting account dialog choose gitlab and https as protocol and then click on refresh personal access token button.
After that in the username and password dialog enter your gitlab username and paste that token you copied it before as your password. Don't enter your gitlab password.
Using Sourcetree version 3.3.4 I am having massive issues with getting the client to authenticate with GitLab EE. GitKraken works fine with the PAT, and I can log in over browser to GitLab EE. I am reasonably certain since I can use another client and PAT authentication, that the trouble is Sourcetree.
I have generated the PAT with api, read_user. I create the account on Sourcetree under Tools >> Opetions >> Authentication >> Add.
Fields selected are "GitLab EE", the site URL, protocol HTTPS. 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.
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.
This is critical and I hope there is a debug method. I have not been able to find a console or any other debug method to get a more detailed error than Authentication failed and the stated way of accomplishing this is not working.
I still have the problem. I tried with GitLab CE and GitLab EE, but with no success.
Protocol is HTTPS and URL looks like https://SEVER.DOMAIN.TOPLEVEL
In login dialog I entered my username and the PAT from https://SEVER.DOMAIN.TOPLEVEL/profile/personal_access_tokens
I was having this issue with 3.1.3 and it turned out I had chosen the wrong version of GitLab in the drop-down (so make sure you have chosen the correct one out of GitLab, GitLab CE and GitLab EE).
Once I had chosen the correct one, entering my GitLab username (i.e. the one after the @ when you click on your avatar in the top-right menu on GitLab) and the PAT (not my GitLab password) I was then authenticated.
over 2 years later and still no answer?
We have a private server running gitlab community edition.
Using my token as password still throws Authentication failed, with no explanation as to why. Other git clients work fine. I really wanted to use sourcetree.
Fix this, or at least give better feedback as to WHY it failed... I am 1000% sure I used correct credentials. I used the token, the token works with other clients, why not sourcetree.