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

Gitlab registry oauth (unknown client) #2688

Closed
rundx opened this issue Jan 30, 2021 · 3 comments · Fixed by #2689
Closed

Gitlab registry oauth (unknown client) #2688

rundx opened this issue Jan 30, 2021 · 3 comments · Fixed by #2689

Comments

@rundx
Copy link

rundx commented Jan 30, 2021

Incase no one noticed, Gitlab registry login is not working anymore
I think they require HTTP Basic authentication using client_id and client_secret along with this request to get the oauth token https://docs.gitlab.com/ee/api/oauth2.html

POST /oauth/token HTTP/1.1
host: gitlab.com
content-type: application/x-www-form-urlencoded
accept: application/json
Content-Length: 56
Connection: close
grant_type=password&username=xxxx&password=xxxxxxx


{
  "error":"invalid_client",
  "error_description":
  "Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method."
}
@bwateratmsft
Copy link
Contributor

Looks like you're correct. We'll have to investigate.

@bwateratmsft
Copy link
Contributor

Looks like OAuth is not a practical solution anymore since it requires users to register an application and provide the app ID and secret in addition to the username and password. Personal access token auth is probably the only reasonable replacement. I'm going to dupe this to #1968, and flag that one for re-triage so we can prioritize appropriately.

@bwateratmsft
Copy link
Contributor

This fix is now released in Docker extension version 1.10.0.

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants