The need for Personal Access Tokens (PATs) in Git While this is not a new issue with Git and password-based authentication, especially when you run into failures like Pushing changes to the remote repositoryI will give it 5 minutes before I hear some of my pals telling me they remember that due to several services such as GitHub have stopped supporting passwordsTip… The following steps will provide a complete solution to this problem.
Authenticating the Authentication Failure
Classic authentication failures include:
Mismatched Credentials: This is things like mistyped usernames or passwords.
Token expired: If you were using an access token, it may be invalid or has already been revoked.
Two-Factor Authentication (2FA): When 2FA is turned on you need to use a PAT not your password
Human error: You may have made a typo when typing your passwordgit access issues Configuration errors:none of this is good news anything as soon you the 【mistakes】 are made from(Mocking SpongeBob source)
How to create a personal access token and use it?
Access GitHub Settings:
Log into your GitHub account.
Yeh step thoda tricky hai, aapko apne Profile Pic par click karna h aur usme Settings me jaake Domain ownership option choose karna padhega.
Navigate to Developer settings in the main sidebar:
Generate a New Token:
The Personal access tokens under which click on Generate new token
Add a note for the token, and choose the necessary scopes (for example – repo to access repositories ).
Click on Generate token, you will not see it again and make sure to copy.
Token is used for GIT Operations :
Use this PAT instead of your GitHub password when prompted for a password by Git (for example, during an git push).
Updating Stored Credentials:
If things will still not work, you can try to remove the stored credentials :
In windows credentials and delete any credential with the type “Git” in it.
For macOSSystem Preferences >
iCloud/Desktop & Documents Folders removes the local copyOn macOSOpen Keychain Access and update or delete the relevant entries;
Consider SSH Authentication:
Another option is to generate SSH keys, which provide a better and more security method of autentication where we don’t have to type the credentials everytime.
Conclusion
You can solve most of the Git authentication error by creating a Personal Access Token and setting up your credentials properly.git-authentication (ad) It not only provides you with additional security, but it also simplifies the process and makes interacting with remotely-stored repositories practically seamless.
