Why are credentials requested on gh repo clone when I am already authenticated with a PAT?

[mimkorn]

Hi, so I was advised by the tool to use a personal authentication token instead of credentials. So I authenticated and the status says I am authed over HTTPS with the PAT. Yet, when I call gh repo clone on a private repo, I am still asked for credentials and then advised again to use a PAT instead.

Is there some security reason why to ask for another PAT, when I am already logged in? Why does it not use my current authentication instead?

[mislav]

I'm sorry that this is confusing!

When your authenticate with GitHub CLI (e.g. via gh auth login), you've authenticated against the GitHub API, but that doesn't 100% ensure that all your git traffic is authenticated. GitHub API and git traffic to GitHub can use separate methods of authentication, and this isn't always clear to users. We aim to improve that in #2944

What you can do to remedy this:

• When doing gh auth login, choose "Yes" for Authenticate git with your GitHub credentials?; or

• Run this locally to configure git authentication:

  git config --global 'credential.https://github.com.helper' ''
  git config --global --add 'credential.https://github.com.helper' '!gh auth git-credential'
  

Hopefully with future versions of GitHub CLI you will not have to worry about this nor run any commands manually.

[kdere]

This did not work for me. So I am logged in with a token

> gh auth status github.com ✓ Logged in to github.com as kdere (~/.config/gh/hosts.yml) ✓ Git operations for github.com configured to use https protocol. ✓ Token: *******************

but I can not do a push on this computer but I can on another

git push origin master remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information. fatal: Authentication failed for 'https://github.com/kdere/ChiantiPy.git/'

also cleared the authentication stuff from ~/.gitconfig

thanks in advance,
Ken

[samcoe]

Since @mislav wrote his previous answer we have added a new command gh auth setup-git that should help make this process smoother. Would you mind trying out that command and seeing if that fixes the issue you are encountering?

[kdere]

where can I find the latest version of gh?

[samcoe]

Without knowing what OS you are using or how you previously installed gh I can only direct you to our installation page https://github.com/cli/cli#installation which has instructions for various OSs. Additionally, you can download our binaries directly from our releases page https://github.com/cli/cli/releases/tag/v2.4.0.

[kdere]

got version 2.4 of gh-cli installed. I am running on openSUSE and installed the repo

gh auth login < ~/mytoken.txt gh auth setup-git

gh/ChiantiPy> git push origin master gh auth git-credential: "erase" operation not supported remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead. remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/<https://secure-web.cisco.com/1H4uU48-RHmxA4XbyQddiJKQn1yyESOE0gOm8B4X8D45FZd2mDXiJ-poR515yRxHhtT9xI5rGR0z1cS70AvUwJP5R9RcCaSEhG4mPaAaTvUYoENkoe_0DnoFhPGw5_t0Fmunynk4SRRJmqcCDZaFFfXUIphtvRungIrsI47NX8aPHNhR4b8Zm6tWTfSs8lgC1aXtMPj0ah76Wu9Ld_AIZjIXddxbPrRdShO5Z6T_kwqh1Zjr9bPtDGCPulSrdch0uXM2N0c7ExiiAIFii8NuFVXXQVdy9L_20NquHuAQJVainByLlhwq6-q6XTHb9n69Ejox5F1Hj1fCSlBFCLDyF2L5x3KbIbnJVh4PSmskq_YHnwdVT5q_d5SPbZJPGK6CvHtYdNE4QIZJCmJkrgi__rAg3Sy8rDVaHU5Sf9oyCCWQGtuOQOn5GTBPxPnhab9j5/https%3A%2F%2Fgithub.blog%2F2020-12-15-token-authentication-requirements-for-git-operations%2F> for more information. fatal: Authentication failed for 'https://github.com/kdere/ChiantiPy.git/<https://secure-web.cisco.com/1jDr9o5Op_2wHvbcWbm5bb85RVlzWcb7xb7kVMbrBQOOyhSmmCzaer2Ymf4iDXggh5kAfY4oQ-hgmXjf4VtW-JAD0bCITjBxGdUUXmHkSBHTaomC_LotKft0CY9YUFI-LDRbh8w947vHenplnRH-LKd9E1KriK8fXdt16tj6h_qTLkWRNfCgZT0q4SNo6aP6BmqgK4fyGNIBC9StXnXG2v7b0Qdi4mNjfjbK03gnINckxB1-NcVwbhCWDkQFbit6Px1IE1pGZ5_Qg0-lj0A2mHMK4MOgxP5c-JbyQ0tnML1WWTUDoWkVWgnW9JJxzaKlfcM0hAOeYXRaW2DYPNrJOa6PaOIW6dHD0GOQWsCyPGbfx3qofxZfDPCeE55QcrmyVwrIXl4HKkhu1y9XvtE7QHXrn6UqMIXsLbwfQ19tikszp4X2o6zZxPIaIGHIL5a8W/https%3A%2F%2Fgithub.com%2Fkdere%2FChiantiPy.git%2F>' so I am still having problems. Ken

[octopyth]

two years after a workaround has been identified, we are still using workarounds