Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No login API accepted for gitlab-ee-13.9.0-ee.0.sles15.x86_64 #175

Open
hmcosta opened this issue Feb 23, 2021 · 3 comments
Open

No login API accepted for gitlab-ee-13.9.0-ee.0.sles15.x86_64 #175

hmcosta opened this issue Feb 23, 2021 · 3 comments

Comments

@hmcosta
Copy link

hmcosta commented Feb 23, 2021

Installed product versions

  • Visual Studio: Professional 2019
  • This extension: 1.0.333

Description

After updating gitlab server to gitlab-ee-13.9.0-ee.0.sles15.x86_64, the login is refused

Steps to recreate

  1. Upgrade the GitLab server to version gitlab-ee-13.9.0-ee.0.sles15.x86_64
  2. Check that the connection on the Visual Studio GitLab extension was broken
  3. Attempt to login on the GitLab server using the GitLab extension

Current behavior

Apparently looks like that after the server update the parameters the client uses are no longer accepted or something else is needed to configure on the server.
Before the server update, was working fine.
imagem

Expected behavior

Should be possible to perform the login

@hmcosta
Copy link
Author

hmcosta commented Mar 13, 2021

Does someone knows if this is a bug or a configuration error?

@piatkowskia
Copy link

I have the same problem when I use host, login and password (V4_Oauth).
Try use login with 2FA (https://github.com/maikebing/GitLab.VisualStudio/blob/master/README.md).
Works for me.

@hmcosta
Copy link
Author

hmcosta commented Mar 27, 2021

I have the same problem when I use host, login and password (V4_Oauth).
Try use login with 2FA (https://github.com/maikebing/GitLab.VisualStudio/blob/master/README.md).
Works for me.

Many thanks @piatkowskia it also worked for me. Spend a lot of time debugging without the 2FA but I just gave up and followed your tip. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants