Login issue within new visual studio project about gitlab.visualstudio HOT 58 CLOSED

Ok thx i will try if this works for me as well

Dont forget:
Deinstall GitLab 1.0.177
Install 1.0.166 from appveyor link
Login to gitlab
Logout
Restart VS, check if it updated then login again

from gitlab.visualstudio.

Yeah, I get the same error. It seems like that password is wrong. But when I try to log in to the gitlab webpage with the same credentials I can log in. So the user name and password are correct. And something with the vs authentication is wrong.

from gitlab.visualstudio.

I have an account on my laptop, it is logged in, and the existing project works (vs2015 community). But now I tried to login to another computer(vs2017 community) with the same credentials (the credentials work on the gitlab website) and I get the same above mentioned errors.

from gitlab.visualstudio.

Yeah, I get the same error. It seems like that password is wrong. But when I try to log in to the gitlab webpage with the same credentials I can log in. So the user name and password are correct. And something with the vs authentication is wrong.

Same here. I can login with same credentials in GitLab (on premise and gitlab.com) but not with the GitLab for VS.

from gitlab.visualstudio.

We have the same problem.
@Tuumke's solution seems to work for us.

from gitlab.visualstudio.

Having issues as well. Using LDAP username + pass, LDAP username + access token, APIv4 and 2FA.

from gitlab.visualstudio.

As a suggestion on how to reproduce, perhaps try using windows Credential Manager to remove the credentials added by the extension. My problems began after losing my primary hard drive, so on a fresh install of windows, fresh install of Visual Studio 2017 Community and the current version of the plugin. Cleaning my credentials does not help, so may be the step you are missing to seeing the fail login attempts.

This would be my suggestion as well. I experienced the issue on a fresh install of VS 2017.

from gitlab.visualstudio.

@Tuumke
https://ci.appveyor.com/project/MaiKeBing/gitlab-visualstudio/history

open a " history build" , find Artifacts page , download it !

from gitlab.visualstudio.

This one works:
https://ci.appveyor.com/project/MaiKeBing/gitlab-visualstudio/builds/20928730/artifacts
1.0.166
Using LDAP + PAT + 2FA + APIv4
Now it updated again automaticly to 1.0.177 and login works :-S in the same way..
My mind is blown..

from gitlab.visualstudio.

We have the same problem.
@Tuumke's solution seems to work for us too.

from gitlab.visualstudio.

I'm getting the exact same issue. Also using VS2017 Community Edition.

from gitlab.visualstudio.

I am getting this exact same issue also on VS2015 Community.

from gitlab.visualstudio.

Same...

from gitlab.visualstudio.

I have the same problem. I get the same screen if I try to log from Team Explorer/Sync or Manage Connections with GitLab APIv3 Oauth2, or GitLab APIv4 Oauth2. If I try to log in with Auto Discovery, it says:

If I open a project that already tracks a remote branch everything works like it should.

I have tried clearing all references to GitLab from Credential Manager and the problem persists.

(Update)
I can clear all of the GitLab entries from Credential Manager, then open a project that already tracks a remove branch. When I attempt to do a fetch it will ask me for my credentials. I can enter them, successfully perform the fetch, then refresh the Credential Manager and see the entries repopulate. I then try to log in from Manage Connections (since I need to clone). If I select Auto Discovery I get the same alert I show above. If I try GitLab APIv3 Oauth2, or GitLab APIv4 Oauth2 I get the following:

from gitlab.visualstudio.

Same, v1.0.176

Besides, sniffing authentication response with HTTP 200 OK gives me that JSON:

{"id":4,"name":"Сорокин Андрей Владимирович","username":"avsorokin","state":"active","avatar_url":"http://mygitlabserver.mycompany.ru/uploads/-/system/user/avatar/4/avatar.png","web_url":"http://mygitlabserver.mycompany.ru/avsorokin","created_at":"2018-12-25T10:09:14.273Z","bio":"","location":"","public_email":"","skype":"","linkedin":"","twitter":"","website_url":"","organization":"","last_sign_in_at":"2019-02-08T08:58:50.336Z","confirmed_at":"2018-12-25T10:09:14.136Z","last_activity_on":"2019-02-08","email":"[email protected]","theme_id":1,"color_scheme_id":1,"projects_limit":100000,"current_sign_in_at":"2019-02-08T11:36:12.421Z","identities":[{"provider":"ldapmain","extern_uid":"cn=сорокин андрей владимирович,ou=mycompany users,dc=mycompany,dc=ru"}],"can_create_group":true,"can_create_project":true,"two_factor_enabled":true,"external":false,"private_profile":false}

from gitlab.visualstudio.

I have the same problem using VS2017Comunity and v1.0.176 as well. Never used it bevore have no existing connections. Not able to make it work.
I created gitlab account by signing in with github account. Just in case it matters...

from gitlab.visualstudio.

Typically, it may be that the user name password is incorrect

from gitlab.visualstudio.

It's not incorrect login issue. Because with same credentials you can clone and then commit/push/fetch/... but you just can login over connect window to browse etc...

from gitlab.visualstudio.

No i just tryed and copy paste password and username from a textfile. Login in VS-Extension faild and login onto gitlab website worked.

from gitlab.visualstudio.

Same problem, login on website works, in VS "Failed to login. Requested value 'AutoDiscovery' was not found."

from gitlab.visualstudio.

Same thing here with VS2017. Any workaround?

from gitlab.visualstudio.

New version 1.0.177, who tested it, what's the problem?

from gitlab.visualstudio.

version 1.0.178:
All the same.

from gitlab.visualstudio.

Version 1.0.178 still has the login issue for me.

from gitlab.visualstudio.

@Tuumke @cjmny @GoodLeak Can you give me a test account?

from gitlab.visualstudio.

I also having the same issue. Test account created.

from gitlab.visualstudio.

I have an account on my laptop, it is logged in, and the existing project works (vs2015 community). But now I tried to login to another computer(vs2017 community) with the same credentials (the credentials work on the gitlab website) and I get the same above mentioned errors.

Same Problem. Pc with vs2017 community logged in 6 months ago and new vs2017 community installation on a laptop dosn't work.
For reproduction you can check if the problem occures in a vm.

from gitlab.visualstudio.

@Tuumke @cjmny @GoodLeak Can you give me a test account?

Sorry, was responding in #17.
It's a private server, so no i cannot give you test account. But, i also created an account on gitlab.com and having same issues and errors.
Just created an account @ gitlab.com to try and see if it works there.
Using server https://gitlab.com with username and password and autodiscovery:

Using server https://gitlab.com with e-mail adress, pass, auto discovery:

Using server https://gitlab.com with username or e-mail, token, auto discovery, 2FA:

from gitlab.visualstudio.

@Tuumke It looks like your user password is incorrect. More details can read
https://github.com/maikebing/GitLab.VisualStudio/blob/master/README.md

from gitlab.visualstudio.

When you login with a user name and password.
For the new version of Gitlab：

https//gitlab.com or your GitLab server
input your email address or username
your password (not the token)
use "GitLab ApiV4 Oauth2" don't use "API v4" as the instructions direct
Two-Factor : Off
For older versions of Gitlab

Your GitLab server
input your email address or username
your password (not the token) 1.use "GitLab ApiV3 Oauth2" or "API v3"
by Brett Winters

When you login with 2FA :
In GitLab, [top right] go to Settings then Access Tokens (left menu)
Enter a name & expire time (optional).
Check off "api" as the scope.
Click "Create Personal Access Token". This will appear in a textbox at the TOP of the page.
In Visual Studio, click "Connect" beside GitLab.
Enter your GitLab Username and paste in the Access Token.
Change it to "API v4" instead of "API v4 OAUTH2".
Make sure "Two Factor Authentication" is CHECKED.
Save. You're DONE.
When you login with LDAP credentials :
If you create a personal access token (https://yourgitlaburl.com/profile/personal_access_tokens) and select 2fa and use your ldap username + your PAT you will be able to login and use the plug-in.

by dominicdejacomo

from gitlab.visualstudio.

I'm getting the exact same issue as @Tuumke and I've tried the same things.
It may be completely unrelated, but I tried connecting GitLab through Sourcetree and received a similar issue with authentication. (It connects to my GitHub just ftine, but not GitLab)

from gitlab.visualstudio.

I'm getting the exact same issue as @Tuumke and I've tried the same things.
It may be completely unrelated, but I tried connecting GitLab through Sourcetree and received a similar issue with authentication. (It connects to my GitHub just ftine, but not GitLab)

Today I also went the SourceTree route but my account credentials worked fine. Also, I am able to work with an existing repo and it works fine, although, the UI is set up in such a way that I believe it 'thinks' it is not connected. Consider the following:

In this project I am able to make changes and sync with the remote server.

However, if I go to the sync tab and attempt the same thing, I see this:

Nothing in that looks like the extension is aware that I have a connection to GitLabs. It doesn't think I track a remote branch, but it is clearly in the settings and functional:

The real issue comes in to play when I need to pull a repo for the first time. In order to do that I need to pass that login on the sync tab and it has been ridiculously unreliable since the first day I installed this extension (like a year ago or more). If I use SourceTree or Git GUI to pull the project I can then manipulate the remote repo using the extension just fine despite the it not being able to figure out what is going on with the login.

from gitlab.visualstudio.

Very strange, I did nothing to change and tried to sign in again on VS after about 5 hrs and it worked first time. Tried on SourceTree and I'm still getting the error.

No idea why

from gitlab.visualstudio.

I can't reproduce the problem, who can debug it?

from gitlab.visualstudio.

just install vs17 on a fresh machine then you can debug it.
I'll try to debug it later,

from gitlab.visualstudio.

Do you have a short instruction in how to debug this?

from gitlab.visualstudio.

https://stackoverflow.com/questions/9281662/how-to-debug-visual-studio-extensions
@Tuumke

from gitlab.visualstudio.

https://stackoverflow.com/questions/9281662/how-to-debug-visual-studio-extensions
@Tuumke

Sorry, that's out of my league i think. And don't have time atm to figure out how exaclty (when i lauchn my solution and select properties, i don't see these options)

from gitlab.visualstudio.

As a suggestion on how to reproduce, perhaps try using windows Credential Manager to remove the credentials added by the extension. My problems began after losing my primary hard drive, so on a fresh install of windows, fresh install of Visual Studio 2017 Community and the current version of the plugin. Cleaning my credentials does not help, so may be the step you are missing to seeing the fail login attempts.

from gitlab.visualstudio.

We're experiencing the same issue on a fresh install of VS 2017 (15.9.7) and Gitlab extension 1.0.177

We run our own instance of Gitlab and can see successful authentications from the extension in the GitLab logs, but the extension responds with:

Failed to login
Please checkyour username or password!
Last tryV4:Not login yet

We are using 2FA, an access token and API V4.

from gitlab.visualstudio.

@banjosteve
When you login with 2FA :
In GitLab, [top right] go to Settings then Access Tokens (left menu)
Enter a name & expire time (optional).
Check off "api" as the scope.
Click "Create Personal Access Token". This will appear in a textbox at the TOP of the page.
In Visual Studio, click "Connect" beside GitLab.
Enter your GitLab Username and paste in the Access Token.
Change it to "API v4" instead of "API v4 OAUTH2".
Make sure "Two Factor Authentication" is CHECKED.
Save. You're DONE.
When you login with LDAP credentials :
If you create a personal access token (https://yourgitlaburl.com/profile/personal_access_tokens) and select 2fa and use your ldap username + your PAT you will be able to login and use the plug-in.

from gitlab.visualstudio.

@banjosteve
When you login with 2FA :
In GitLab, [top right] go to Settings then Access Tokens (left menu)
Enter a name & expire time (optional).
Check off "api" as the scope.
Click "Create Personal Access Token". This will appear in a textbox at the TOP of the page.
In Visual Studio, click "Connect" beside GitLab.
Enter your GitLab Username and paste in the Access Token.
Change it to "API v4" instead of "API v4 OAUTH2".
Make sure "Two Factor Authentication" is CHECKED.
Save. You're DONE.
When you login with LDAP credentials :
If you create a personal access token (https://yourgitlaburl.com/profile/personal_access_tokens) and select 2fa and use your ldap username + your PAT you will be able to login and use the plug-in.

Thanks @maikebing, unfortunately, we have done all of that. Our GitLab instance even recognizes the successful authentication, but the extension seems to be blocking somewhere.

from gitlab.visualstudio.

@maikebing btw, we run on 1.0.177 but there are no release notes yet?
https://github.com/maikebing/GitLab.VisualStudio/blob/master/CHANGELOG.md
What did you change between V1.0.160 and 1.0.177? And can we somehow download previous versions? For GitHub there is a revert button

But for GitLab it's just uninstall / disable

-edit-
Found 1.0.178 http://vsixgallery.com/extension/54803a44-49e0-4935-bba4-7d7d91682273/
Testing now
Same issue :( Is there any archive where i can download previous versions?

from gitlab.visualstudio.

@Tuumke

Here may be the only difference

from gitlab.visualstudio.

Wait.. 1.0.178 is newer then 1.0.177 :-O
Can you get me the older releases?

from gitlab.visualstudio.

Ok thx i will try if this works for me as well

from gitlab.visualstudio.

1.0.178 works fine with APIv4 + 2FA checked in for all gitlab installations.

from gitlab.visualstudio.

I have the same issue with 1.0.177

from gitlab.visualstudio.

Otto Milvang

Login doesn't work.
From wireshark I saw that I got an access token and also got a json
{
"id": 2,
"name": "Otto Milvang",
"username": "otto",
"state": "active",
"avatar_url": "https://www.gravatar.com/avatar/...",
"web_url": "http://192.168.10.10/otto",
"created_at": "2016-12-23T13:16:06.975Z",
"bio": null,
....
"projects_limit": 1000,
"current_sign_in_at": "2019-03-06T09:01:39.016Z",
"identities": [],
"can_create_group": true,
"can_create_project": true,
"two_factor_enabled": false,
"external": false,
"private_profile": null,
"is_admin": true
}
Still the response says "Not login yet"

from gitlab.visualstudio.

I was able to get this working as usual by reverting to the older version as well:

@Tuumke
https://ci.appveyor.com/project/MaiKeBing/gitlab-visualstudio/history

open a " history build" , find Artifacts page , download it !

Sorry, not at the problem machine so can't check the version. Will edit.

from gitlab.visualstudio.

Unfortunately reverting is not working for me, because there is no "Publish to gitlab" with login button under sync in older versions for some reason...
EDIT: I was able to login in version 1.0.0.122. Then I updated to 1.0.166 and finally 1.0.179 and I'm still connected. But I don't have any new options in Team Explorer, that are here

from gitlab.visualstudio.

Current version on Visual Studio Gallery did not work for me either, the AppVoyer version does.

from gitlab.visualstudio.

Also running into this problem. Migrated a project to Gitlab this morning and am now trying to get the Gitlab extension running in VS. At this point I've lost 3 hours just trying to get this thing going. 30 mins to find where to log in, and now that I've found that I'm unable to log in anyway. Hopefully these issues will be ironed out. For now, I may have have to revert to the raw git integration VS provides. Not ideal.....

from gitlab.visualstudio.

Hi, everyone, please test the new version! If you have any questions, please reply to me.

https://ci.appveyor.com/project/MaiKeBing/gitlab-visualstudio/builds/23132899/artifacts

from gitlab.visualstudio.

Seems to work! Or, at least, i logged in! Thanks!

from gitlab.visualstudio.

No problem with login in 1.0.180 with GitLab CE (I tried password and token).
In Team Explorer Home I can see only one new button (Graphs) and after click it only shows "Object reference not set to an instance of an object." on top of the panel.

EDIT: I'm testing v1.0.182 and login still works but I can't logout now.

from gitlab.visualstudio.

Also running into this problem. Migrated a project to Gitlab this morning and am now trying to get the Gitlab extension running in VS. At this point I've lost 3 hours just trying to get this thing going. 30 mins to find where to log in, and now that I've found that I'm unable to log in anyway. Hopefully these issues will be ironed out. For now, I may have have to revert to the raw git integration VS provides. Not ideal.....

@Ddog800, any chance you could share where to log in? I'm looking too. Documentation is poor. In Team Explorer, all I see is a message "Gitlab unlimited free repositories and collaborators..."

Thanks

Found it!

As referenced here, it's in the most illogical place ever!!

For others, struggling: Team Explorer > Home > Sync

@maikebing, perhaps you could address this issue or at least make it clear in the documentation?

Thanks

from gitlab.visualstudio.

I have the same problem using VS2017Comunity and v1.0.176 as well. Never used it bevore have no existing connections. Not able to make it work.
I created gitlab account by signing in with github account. Just in case it matters...

I had this issue too. You need to go to password settings on gitLab web site and set it. If you login with github account is your gitLab password not defined, and that's why you cannot connect.

from gitlab.visualstudio.