"Support for password authentication was removed. Please use a personal access token".
During my earliest stage in the tech space as a budding developer, I had hitches with GitHub. I mean, every developer experiences this. I tried to run git operations. I got the error message that indicated that password authentication was removed and I would need to use a personal access token. Thanks to instructions provided by my technical mentor, I was able to navigate through this challenge.
This article seeks to guide you through this process if you are at this phase in your programming journey.
What is GitHub Personal Access Token?
Personal Access Token is a long string of characters used to authenticate a user when accessing the GitHub server instead of password-based authentication. In other words, if you want to run git operations, you will be required to generate a Personal Access Token rather than use a password you create for yourself.
Features of GitHub Personal Access Token
- It is unique
- It is a long string of character combinations
- It is more secure than passwords
- It is hard to read
- You have to generate it
- You can decide if it expires or not (It is not advisable to create PAT with no expiry date)
- It is revocable
- It allows you to control access to certain features
How To Create A GitHub Personal Access Token
Step 1: Click your profile on GitHub:
Step 2: Go to settings:
Step 3: Scroll down and click "Developer settings" at the bottom left:
Step 4: Click "Personal access tokens":
Step 5: Click "Generate new token":
Step 6: Type in your password and confirm access:
Step 7: Insert a note:
This could be the project name.
Step 8: Select the number of days before it expires:
Step 9: Select scopes to grant and limit access to certain features:
Step 10: Click "Generate token":
Step 11: Copy the token:
Make sure you copy the token and keep it safe so you can use it. If you don't, you will have to generate a new one to perform git operations.