-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Unable to Persist Credentials and Not Getting Prompted for Auth #633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm experiencing something similar with 2.35.1.Windows.2 I downgraded to 2.35.0.Windows.1 and that fixed the issue. I suspect there is a critical bug in 2.35.1.Windows.2.
|
Thanks. I tried downgrading to this version, but the issue remains for me. |
Well... mine is not working again. Now with a new error:
This is killing me. I'm dead in the water. Git is 100% unusable. |
@gbrac @Elsewhere42 - Are you SSH'ing into your Windows machines by chance? |
No, I am not. |
@Elsewhere42 - I'm assuming you also were not prompted to authenticate? Would you both mind running the below command, re-running your push/clone commands to repro the issue, then dropping the log file that was created in your
|
@ldennington Thanks for the tip about the log file. Over several days I spent many hours searching for a logging command but never found one. That was exactly what I needed.
It looks like a Proxy Authentication error. Is there any information available about how to setup Proxy Authentication on Git?
|
Would you mind trying the steps outlined here? |
This is the only error or exception I have in that log. Everything else reports OK:
|
@gbrac - apologies! I edited my above comment. Would you mind following the new instructions and sending along those logs? |
For future reference, you can find details on troubleshooting (including logging) here. |
I attempted to do the git push from the command line (instead of from within Visual Studio Pro 2022), and it appears to work. So, the issue appears to involve Visual Studio and GCM Core. I previously had GCM for Windows (the non-core version), and that worked, other than it would ask for credentials every time (instead of caching them). It appears now that only GCM Core is available, however. |
This will be the same underlying problem. GCM for Windows will have been prompting you each time because it was failing to persist credentials in the store. GCM (Core) is instead failing up-front because it has detected persistence is broken for some reason. Please can you try changing the backing store that is being used to one that is more reliable? git config --global credential.credentialStore dpapi This will tell GCM to write credentials to encrypted files under |
Yes, I am SSHing to a windows machine. Everything works seamlessly when I RDP to the remote. But when I SSH, it says unable to presiste credentials. Could you please let us know how to solve it in SSH case? |
After a little bit of reading, it turns out that docs explicitly warn that wincredsman codesn't work for SSH and advise for a different one instead. https://github.com/git-ecosystem/git-credential-manager/blob/main/docs/credstores.md |
it fixed my issue that it "Unable to persist credentials with the 'wincredman' credential store." |
I had this same issue and this resolved my issue as well |
When pushing or pulling to Azure DevOps git repo, I do not get prompted for credentials and it fails. Running git-credential-manager-core diagnose, I get: System.Exception: Unable to persist credentials with the 'wincredman' credential store.
OK ] Environment
[ OK ] File system
[ OK ] Networking
[ OK ] Git
[FAIL] Credential storage
[ OK ] Microsoft authentication (AAD/MSA)
[ OK ] GitHub API
Diagnostic summary: 6 passed, 0 skipped, 1 failed.
The text was updated successfully, but these errors were encountered: