GitHub is a popular platform for version control and collaboration, but in August 2021, GitHub removed support for password authentication for HTTPS URLs. This means that if you try to clone a repository using an HTTPS URL and authenticate with a password, you will receive the following error message: “Support for password authentication was removed on August 13, 2021.” Fortunately, you can fix this issue by switching to a personal access token (PAT) or an SSH URL.
I was trying to push my latest committed code to the remote GitHub repository, but faced the following error message:
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.
fatal: Authentication failed for 'https://github.com/collabnix/reponew'
To fix the “Support for password authentication was removed” error in GitHub, you need to switch to using a personal access token (PAT) instead of a password for authentication. Here are the steps to follow:
Option 1: Use a Personal Access Token (PAT)
Step 1. Create a personal access token (PAT) on GitHub
Login to your GitHub account. Go to Settings.
Step 2. Generate a new token
Select “Developer settings,” and then “Personal access tokens.”
Next, you need to generate a new token by selecting the “Generate new token” button. Give your token a name and select the scopes you need. For cloning repositories, you need to select the “repo” scope.
Step 3. Copy the token to your clipboard.
When prompted for your GitHub credentials while cloning a repository using an HTTPS URL, paste your PAT as your password.
Option 2: Use an SSH URL
Alternatively, you can configure Git to use your PAT for all future interactions with GitHub by running the following command in your terminal:
git config --global credential.helper store
This command will save your credentials to a local file, so you don’t have to enter them every time you interact with GitHub. You can then enter your GitHub username as usual, and your PAT as your password.
Keep in mind that using an SSH URL to clone a repository is a more secure and recommended option, as it allows you to authenticate using your SSH key instead of a password or PAT.
Further Reading
-
Docker and Wasm Containers – Better Together
Learn how Docker Desktop and CLI both manages Linux containers and Wasm containers side by side.
-
Containerization: The Secret Force Driving Tech Stocks’ Rapid Ascent
The tech industry is subtly transformed by containerization, driving many rapidly expanding businesses. Containers have changed software development by enabling companies to grow and deliver applications effectively. By utilizing this technology, firms like Google and Netflix have significantly increased their agility, scalability, and cost control. However, why is containerization so crucial for rapidly expanding tech…
-
Cloud-Native Technology: A Game Changer for Tech Investors
Cloud-native technology is transforming the tech investment landscape, offering unprecedented scalability and flexibility for businesses. As more industries shift to cloud-native environments, investors are presented with lucrative opportunities. But what’s driving this surge? Understanding the forces behind this shift and the growth potential is vital for any tech investor looking to stay ahead in a…
-
How to Run AWS CLI in Docker
This document provides a step-by-step guide on how to run the AWS Command Line Interface (CLI) within a Docker container. The AWS CLI is a powerful tool that allows users to interact with AWS services from the command line. By using Docker, you can create a consistent environment for running the AWS CLI without needing…