将SSH密钥添加到Github后，为什么不能继续使用https对git进行身份验证？

Question

• In the past, I've cloned repos with https authentication.
• Recently, I started using SSH authentication.
• When setting up SSH with Github, I also changed my main Github password.

Whenever I enter some old cloned repository on my local drive, which is still using https, I'm no longer allowed to eg git push:

Username for 'https://github.com': MYUSERNAME
Password for 'https://MYUSERNAME@github.com':
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/USER/REPO.git/'

• The .git/config is untouched from back when the repository was cloned using https, so the url in this file is set to https://github.com ...
• I'm entering my NEW password.

I could now change the url in .git/config to use the SSH keys: url = git@github... . But I'd like to keep using https here. How can I do that?

Answer 1

SSH key is for SSH connection and not HTTP(S).

If your repository already has a remote repository setup with HTTP, you can easily change it with the command git remote set-url origin git@github.com:USER/REPO.git

Answer 2

Turns out this didn't have anything to do with SSH keys being added. I also added two-factor authentication (2FA) which was the reason I started having issues.

The solution is to create a token and use that instead of the password when managing a repository via HTTPS: https://help.github.com/articles/https-cloning-errors#provide-access-token-if-2fa-enabled