Replies: 3 comments 1 reply
-
This is the correct way to configure this. If you are in doubt whether that setting is still in effect, call If you still doubt that Git uses that backend, run your
If, for some reason, you're using the OpenSSL backend, you will see something like this instead:
Having said that, I suspect that the problem is not so much the backend used by Git, but I suspect that the store somehow loses that cert instead. Hopefully you can figure it out! |
Beta Was this translation helpful? Give feedback.
-
These troubleshooting steps are helpful. I'll have my team try this and report back here with additional troubleshooting information if we still cannot figure out the root cause. This may not be an issue with the installer, but I'm verily certain it is not an issue of the Windows Certificate Store losing the cert. All HTTPs traffic on our machines is routed through this service as sort of a proxy for packet inspection of otherwise encrypted traffic. We only see the issue with Git, and only on Windows (we have WSL and MacOS environments that do not experience this). If the store was losing the certificate all my development tools would start failing with a similar issue and I would see warnings of invalid certs in my browser, etc. And reinstalling Git for Windows would not re-add the certificate to the store as this is something proprietary to our organization. |
Beta Was this translation helpful? Give feedback.
-
Everything was working fine yesterday. After starting up this morning, I am seeing the issue as usual. Here is what I see. After further thought on this, it looks like I'm losing connection to the Windows Credential Manager store, and not the Windows Certificate Store. I normally do not get prompted for a password after the first interaction with a repo as credentials are stored in the Windows Credential Manager. I am also usually prompted in a web browser pop-up to SSO to AzDO. When I'm seeing the issue after a restart I get prompted in the terminal for credentials, and my normal credentials do not work.
This does make me think the schannel setting in my user scoped .gitconfig is getting picked up and is effective.
I then go to uninstall Git for Windows and reinstall. The reason I think this is an install settings issue is when I go to reinstall, my installer selections are not persisted. That might be a red herring and happening because I uninstall first. But I'd like to figure out how to check before I uninstall. For example, I always select schannel but it isn't selected when I reinstall. I also always select I do not see an option for selecting Windows Credential Manager in the installer, but I do see the default of using the cross-platform credentials manager which is still selected during reinstall. After the reinstall it works again with no other changes or having to authenticate.
|
Beta Was this translation helpful? Give feedback.
-
I'm having an issue where every time I restart my machine, it seems like some settings I chose in the installer are getting reverted. Specifically, I want to use schannel to allow Git to trust certs in the Windows certificate store to trust a company CA we have for self-signed certs. It works like a charm on the initial install. But as soon as I restart Windows, something changes and Git no longer trusts certs deployed to the Windows Certificate store again. The workaround for me is to uninstall Git for Windows and reinstall it with schannel enabled again. My theory is something on our network, group policy or otherwise, is changing the settings and breaking my development environment. I'd like to review whether these settings are not getting wiped out after a restart. Open to any other ideas to troubleshoot as well.
I have put the following in my .gitconfig, but it does not seem to be effective and the installer doesn't add this entry. So there must be something else Git for Windows looks at for this or I do not have the correct .gitconfig entry.
Beta Was this translation helpful? Give feedback.
All reactions