Git-Credential-Manager-for-Windows icon indicating copy to clipboard operation
Git-Credential-Manager-for-Windows copied to clipboard

Secure Git credential storage for Windows with support for Visual Studio Team Services, GitHub, and Bitbucket multi-factor authentication.

Results 82 Git-Credential-Manager-for-Windows issues
Sort by recently updated
recently updated
newest added

This PR adds support for storing PAT tokens to Azure KeyVault instead of Windows Credential Manager. This simplifies deployment and secret management for Azure VMs that use Git (build machines,...

**Which Version of GCM are you using ?** From a command prompt, run ``git credential-manager version`` and paste the output. ``` Git Credential Manager for Windows version 1.20.0 ``` **Which...

**Which Version of GCM are you using ?** 1.20.0 From a command prompt, run ``git credential-manager version`` and paste the output. **Which service are you trying to connect to** *...

**Which Version of GCM are you using ?** Git Credential Manager for Windows version 1.19.0 **Which service are you trying to connect to** * [x] Azure DevOps * [ ]...

Git version **1.18.1.windows.1** having problems when the passwords are changed. It is not auto prompting for new password. It used to work fine in **1.16.2.windows.1**

more-info-needed

[GitHub will disable password-based authentication](https://github.blog/changelog/2019-08-08-password-based-http-basic-authentication-deprecation-and-removal/) on APIs Git Credential Manager for Windows uses to create tokens. As a result, **GCM for Windows will no longer be able to create new...

Git Credential Manager for Windows is no longer being maintained. The cross-platform [Git Credential Manager Core (GCM Core)](https://aka.ms/gcmcore) is the official replacement. GCM Core is included as an optional component...

* This is related to https://github.com/microsoft/Git-Credential-Manager-for-Windows/issues/749 * Usage example: * We can use different GitHub accounts for `https://github.com/user/repo`, `https://[email protected]/user/repo` and `https://[email protected]/user/repo`

For basic authentication, erase protocol://host with matching username, as well as protocol://username@host. Should resolve #793, should resolve #703, may resolve #750, may resolve #817, for BasicAuth