A password is suddenly asked on my token access to github, and even the error message quote it as outdated. #68516
Replies: 7 comments 10 replies
-
I understand how authentication changes can be both surprising and frustrating. Thank you for reaching out, I'll try to clarify the situation for you.
Yes, GitHub made a significant change by discontinuing support for password-based authentication for repository operations. Your method of embedding the access token directly in the URL, though previously functional, is now discouraged due to security concerns. It can expose the token in command-line histories, logs, and other insecure places. Instead, GitHub recommends using Personal Access Tokens (PAT) in a more secure manner or adopting SSH keys. The key distinction between the outdated method you employed and the modern approach is in the security and handling of these tokens:
The password prompt is a general feature of Git, not solely a GitHub-specific function. Git is engineered to interface with a myriad of hosting platforms, each with individual authentication systems. Therefore, even if GitHub doesn't support password prompts anymore, Git will present this prompt when it deems authentication necessary. Furthermore, I'd like to highlight the benefits of using SSH Keys which I personally couldn't recommend more:
To set up SSH keys, you'd produce a key pair (public and private). Your public key is added to GitHub, while your private key stays secure on your machine. The crucial advantage here is that the private key never needs to be shared or transmitted. For additional details on using SSH keys with GitHub, you can explore this GitHub documentation. I hope this helps! Best regards |
Beta Was this translation helpful? Give feedback.
-
I am sorry but I don't understand this at all. I am locked out of imporntant Repos suddenly late at night with the same message:
I have absolutely no idea, why that message is suddenly displayed (the token was previously stored in the credential manager). The linked URL in that error message is completely unhelpful. The link to the documentation you attached is also completely unhelpful. I have my ssh key even setup in GitHub. I know ssh. I have my PAT stored in an environment variable. Yet my workflow/muscle memory is still with https clone/remotes. If you break workflows, please give us a simple step to fix this (e.g.: "enter these 3 commands to switch to ssh remote or enter these 3 commands to setup your git credential store newly"). I have to search for random Stackoverflow Threads on Google to fix this (still unsuccessfully ) because i have no idea from the error message why I suddenly can't access my repos anymore and what the solution is. Not cool! |
Beta Was this translation helpful? Give feedback.
-
I hope you're doing well. Just a gentle reminder about our previous discussion. If you find the answers provided satisfactory and helpful, marking the thread as answered would greatly help my profile and contributions be recognized. It's a free and small gesture that would mean a lot. Thank you for your consideration. Best regards |
Beta Was this translation helpful? Give feedback.
-
Hey there! 👋 Thanks for posting in the GitHub Community, @ThibauldMichel! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. Also, if you did receive an answer to your question here, I would encourage you to mark the response as the answer so that it can help others who have similar questions find the answer in the future. I've gone ahead and moved this to the correct category for you. Good luck! |
Beta Was this translation helpful? Give feedback.
-
Useless Responses!!! |
Beta Was this translation helpful? Give feedback.
-
remote: Support for password authentication was removed on August 13, 2021. can someone give me the correct steps to solve this issue? |
Beta Was this translation helpful? Give feedback.
-
POSSIBLE SOLUTION When you asked for:
This is not a password — it's a personal access token. At least in my case 🙈 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have set up my local git to access to Github via access token using this command:
git push https://<GITHUB_ACCESS_TOKEN>@github.com/<GITHUB_USERNAME>/<REPOSITORY_NAME>.git
Until recently it worked well.
But for an unknown reason, a password was asked when I used the same command line yesterday.
Ironically, the error message itself quote this authentication method is outdated.
On branch master
nothing to commit, working tree clean
Password for 'https://<GITHUB_ACCESS_TOKEN>@github.com':
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/<GITHUB_USERNAME>/<REPOSITORY_NAME>.git/
So my questions are:
Beta Was this translation helpful? Give feedback.
All reactions