- Published on
The New HTTPS Authentication to Github
- Authors
- Name
- interglobalmedia
- @letsbsocial1
Authenticating to Github
via HTTPS
using a username
and password
is no longer a valid way of connecting to Github
via the Command Line
(Mac
) or Command Prompt
(Windows
). As of August 13, 2021
, it has been replaced with Personal Access Tokens
.
This means that when you get to either the Git Command
git commit
, or if you manage to get past that one and onto push -u origin master
or git push origin master
, you will not be able to push
your changes to your remote repository
on Github
. This is if you are on a Mac
.
For a full explanation of what happens when you try to use the old Github authentication
via https
to push your local commits
to your remote Github repository
, please visit the following link on stackoverflow
: Support for password authentication was removed. Please use a personal access token instead
I did not know about this because I have been using SSH
since the beginning. And those of us using SSH
have not been affected. This protocol
is even more secure
than the personal access token authentication
! However, I did walk a student on a Mac
through this, and the Github docs
were great about creating a personal access token
. What we also did, which is not mentioned anywhere, but will make your life easier, is after you create the personal access token
, and are ready to implement it for the first time, do it from the Command Line
(Terminal
) and NOT VS Code
’s Integrated Terminal
. You probably would encounter permission issues
there since you will not have used your personal access token
yet. After you HAVE used it, it will be saved to your keychain
, and then will no longer have issues
with VS Code
.
For those on Windows OS
, it is much easier. I did not even need to use a personal access token
when using VS Code
from inside the Integrated Terminal
. I did not write down the process at the time, but the following link from stackoverflow
goes into detail about the new Github authentication
via HTTPS
replacing the old one covering all OS
: Support for password authentication was removed. Please use a personal access token instead
Other helpful links are: