Home
The Git Credential Manager for Windows (GCM) provides secure Git credential storage for Windows. It's the successor to the Windows Credential Store for Git (git-credential-winstore), which is no longer maintained. Compared to Git's built-in credential storage for Windows (wincred), which provides single-factor authentication support working on any HTTP enabled Git repository, GCM provides multi-factor authentication support for Visual Studio Team Services, Team Foundation Server, and GitHub.
To see learn how the GCM works. Checkout our new wiki page with more details.
This project includes:
- Secure password storage in the Windows Credential Store
- Multi-factor authentication support for Visual Studio Team Services
- Two-factor authentication support for GitHub
- Personal Access Token generation and usage support for Visual Studio Team Services and GitHub
- Non-interactive mode support for Visual Studio Team Services backed by Azure Directory
- Kerberos authentication for Team Foundation Server (see notes)
- Optional settings for build agent optimization
This is a community project so feel free to contribute ideas, submit bugs, fix bugs, or code new features. For detailed information on how the GCM works go to the wiki.
To use the GCM, you can download the latest installer. To install, double-click Setup.exe and follow the instructions presented.
When prompted to select your terminal emulator for Git Bash you should choose the Windows' default console window, or make sure GCM is configured to use modal dialogs. GCM cannot prompt you for credentials, at the console, in a MinTTY setup.
You don't. It magically works when credentials are needed. For example, when pushing to Visual Studio Team Services, it automatically opens a window and initializes an oauth2 flow to get your token.