Skip to content

Git Clone not working after authentication via auth login --token

Checklist

  • I'm using the latest version of the extension (Run glab --version)
    • Extension version: glab 1.76.2 (d8e6f278)
  • Operating system and version: docker image gitlab/glab:v1.76.2
  • Gitlab.com or self-managed instance? gitlab.com
  • GitLab version (if self-managed) GitLab version here (Use the version endpoint, like this: gitlab.my-company.com/api/v4/version)
  • I have performed glab auth status to check for authentication issues
  • Run the command in debug mode (like DEBUG=true glab mr list) and attach any useful output

Summary

I'm authenticating with a access token and after that git clone is not working anymore as compared to version 1.74.0

After authenticating via interactive mode, git cloning goes successfully

Environment

  • OS: Linux 6.6.105+ x86_64
  • SHELL:
  • TERM: xterm
  • GLAB: glab 1.76.2 (d8e6f278)

Other:

Steps to reproduce

glab auth login --token <access token>
git config --global --add credential."https://gitlab.com".helper "!/usr/bin/glab auth git-credential"

git clone <repo>

What is the current bug behavior?

Cloning goes in error

What is the expected correct behavior?

Cloning goes succesful

Relevant logs and/or screenshots

Cloning into ''... remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See https://gitlab.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for ''

Possible fixes

I don't know, sorry

Edited by Michele Allevi
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information