0

For the last three weeks I have been using the OSX keychain to manage my GitHub credentials. Whenever I need to pull in an update, I do the usual:

git pull origin master

With this command, the keychain then pops up and requests my password, which I type, and then the command that was entered in the command line executes.

Suddenly this morning, I go to pull in another change, and it now asks in the command line for my user name and password. Then I get the usual error:

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.

I have worked on this for some time and don't get why the methods in other questions aren't working. I have followed these other posts with no luck

osxkeychain

update git

credential helper and ssh-add -L answers

matt
  • 45
  • 8
  • 2
    You need to use a personal access token instead of your password when asked for your password. – bk2204 Dec 02 '21 at 02:36
  • @bk2204 thanks, it was the use of the term "password" in lieu of "personal access token" that threw me off! – matt Dec 02 '21 at 14:40

1 Answers1

1

First, this has nothing to do with ssh-add, used to cache private SSH key passphrase.

Second, this has to do with GitHub new policy: Git password authentication is shutting down.

You need to use a PAT (Personal Access Token) instead of your GitHub account password, as described in "Dealing With GitHub Password Authentication Deprecation" by Antonello Zanini, and described here.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • thank you very much! I think it was separating some of these concepts that helped. If anyone else stumbles across this, when the command line asks for your password, you instead provide the personal access token, as VonC said. That overlap of the names password/PAT threw me off. – matt Dec 02 '21 at 14:27