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

Cannot use personal access token to connect to GitLab #1968

Closed
tecandrew opened this issue May 12, 2020 · 6 comments · Fixed by #2689
Closed

Cannot use personal access token to connect to GitLab #1968

tecandrew opened this issue May 12, 2020 · 6 comments · Fixed by #2689

Comments

@tecandrew
Copy link

Issue Type: Bug

  1. Create personal access tokon on GitLab (with API access)
  2. Add Gitlab registry provider
  3. Use Gitlab username (not email) when prompted
  4. Login with token

Extension version: 1.1.0
VS Code version: Code 1.45.0 (d69a79b73808559a91206d73d7717ff5f798f23c, 2020-05-07T16:10:24.511Z)
OS version: Linux x64 5.4.0-29-generic snap

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 2764)
GPU Status 2d_canvas: unavailable_software
flash_3d: disabled_software
flash_stage3d: disabled_software
flash_stage3d_baseline: disabled_software
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: disabled_off_ok
video_decode: disabled_software
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: unavailable_software
webgl2: unavailable_software
Load (avg) 1, 1, 1
Memory (System) 15.52GB (0.30GB free)
Process Argv --force-user-env --no-sandbox --unity-launch --no-sandbox
Screen Reader no
VM 0%
DESKTOP_SESSION ubuntu
XDG_CURRENT_DESKTOP Unity
XDG_SESSION_DESKTOP ubuntu
XDG_SESSION_TYPE x11
@bwateratmsft bwateratmsft changed the title 401 Unauthorized error when connecting to Gitlab Registry Cannot use personal access token to connect to GitLab May 13, 2020
@dbreshears dbreshears added this to the Future milestone May 15, 2020
@bwateratmsft bwateratmsft modified the milestone: Future May 15, 2020
@niikoo
Copy link

niikoo commented Aug 11, 2020

Same problem here. It returns 401

@M-Whitaker
Copy link

M-Whitaker commented Aug 24, 2020

Same issue as well. Is there a work around known for this?

@UNRULYEON
Copy link

Logging in returns 400 for me.

Extension version: 1.8.1
VS Code version: Code 1.52.0 (940b5f4bb5fa47866a54529ed759d95d09ee80be, 2020-12-10T22:46:53.673Z)
OS version: Darwin x64 20.1.0

@mvaschetto
Copy link

mvaschetto commented Jan 1, 2021

I get error code 400 too, using gitlab username or email with gitlab access token
docker login registry.gitlab.com works with the same access token.

Extension version: v1.9.0
VS Code version: Code 1.52.1 ea3859d4ba2f3e577a159bc91e3074c5d85c0523 x64
OS version: Debian buster kernel 4.19.0-12-amd64

@bwateratmsft
Copy link
Collaborator

Marking this for re-triage, and making this a bug instead of enhancement. OAuth is no longer realistically an option since it now requires a client app ID and secret, so personal or project access tokens are basically the only option. Using GitLab is blocked until we implement this.

@bwateratmsft
Copy link
Collaborator

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.

7 participants