Adding Git credentials on Windows

git bash github

158,145

Solution 1

Ideally, you should enter:

git config --global credential.helper manager-core

Then your password would be stored in the Windows Credential Manager.
See more at "Unable to change git account".

On the first push, a popup will appear asking for your credentials (username/password) for the target server (for instance github.com)

If not, that might means your credentials were already stored.
If they are incorrect, a simple git credential-manager reject https://github.com will remove them (on Windows, again. On Mac: git credential-osxkeychain erase https://github.com)

With Git 2.29 (Q4 2020), the parser in the receiving end of the credential protocol is loosen to allow credential helper to terminate lines with CRLF line ending, as well as LF line ending.

See commit 356c473 (03 Oct 2020) by Nikita Leonov (nyckyta).
^{(Merged by Junio C Hamano -- gitster -- in commit 542b3c2, 05 Oct 2020)}

credential: treat CR/LF as line endings in the credential protocol

^{Signed-off-by: Nikita Leonov}
^{Signed-off-by: Johannes Schindelin}

This fix makes using Git credentials more friendly to Windows users: it allows a credential helper to communicate using CR/LF line endings ("DOS line endings" commonly found on Windows) instead of LF-only line endings ("Unix line endings").

Note that this changes the behavior a bit: if a credential helper produces, say, a password with a trailing Carriage Return character, that will now be culled even when the rest of the lines end only in Line Feed characters, indicating that the Carriage Return was not meant to be part of the line ending.

In practice, it seems very unlikely that something like this happens. Passwords usually need to consist of non-control characters, URLs need to have special characters URL-encoded, and user names, well, are names.

However, it does help on Windows, where CR/LF line endings are common: as unrecognized commands are simply ignored by the credential machinery, even a command like quit\r (which is clearly intended to abort) would simply be ignored (silently) by Git.

So let's change the credential machinery to accept both CR/LF and LF line endings.

While we do this for the credential helper protocol, we do not adjust git credential-cache--daemon^(man) (which won't work on Windows, anyway, because it requires Unix sockets) nor git credential-store^(man) (which writes the file ~/.git-credentials which we consider an implementation detail that should be opaque to the user, read: we do expect users not to edit this file manually).

Solution 2

sorry, nothing worked for me (using msys git 2.33.0), here is my solution:

$ git config --global credential.helper store

go to some source directory

$ git add . && git commit -m "some commit" && git push origin master
Username for 'https://github.com': <type user name here>
Password for 'https://<typed user name>@github.com': <type generated token here>

Solution 3

I tried many things but the Windows Credentials did not added credential for Git. Then I did the following simple action and it resolved my issue.

I removed the related credentials from the Windows Credentials Manager.
Then I opened the Git Bash from the project folder.
Then wrote "git fetch origin" command.
Git Bash first asked for the username and then for the password.

Then I checked the Windows Credentials Manager... Voilaaaa ! It now shows a credential like "git:http://username@address"

I tried to add somethings like "[credential] helper = manager/wincred" things in the config file but after this solution no need for that part, I deleted that [credential] section. Some says that this may be because of your git server is not using https. If it is using https may be you can find different solutions. I still have a goofy like smile on my face

Solution 4

I normally prefer to clone my Git repositories using SSH links. Here are my steps for Windows:

Generate a public/private key pair through PuTTYgen.
Add the public key to my GitHub account.

By doing this, I can easily clone my repositories without needing to use my GitHub account password.

Solution 5

I had a related problem using Windows 10 Pro and Git-2.23.0-64-bit. After I had to change my Gitlab password, fatal: Authentication failed for did occur when- and wherever I tried to push/ pull/... a rep. For me, the following worked out:

Remove git including the respective folders on C: and Install git anew without(!) enabling the Git Credential Manager option in the configuration steps

Afterwards, when I tried to push my rep., the credential manager asked for my credentials one time. Now everything is ok again.

View more solutions

158,145

Author by

PJ Tikalsky

Updated on July 08, 2022

Comments

PJ Tikalsky almost 2 years

I am on a Windows 10 system and am trying to add my credentials to Git in Git Bash. I cannot find a way to store my password.

I checked GitHub's documentation, which said just to enter the line git config --global credential.helper wincred, but that didn't seem to make sense, as there's not prompt to enter a password. I checked Git's documentation, which said to use command git credential-store --file ~/git.store store and fill in all prompts. The bash emulator wasn't able to read the credentials.

Finally, I tried to add my password like I added my email, via git config --global user.password "5ecre7" but after running a sample git clone on a repository I made it responded that I didn't have the access rights. Is there a way to fix this?
PJ Tikalsky over 6 years

Okay. do I need to find the SSH URL for my repo if i clone it, or do I just use my public key?
Raza Mehdi over 6 years

Yes you need both.
JACH almost 4 years

For some reason the command to remove the credentials hung up for me. I found the credentials at Control Panel -> Credential Manager -> Windows Credentials -> Generic Credentials and removed them.
VonC almost 4 years

@JACH That will work indeed. As seen in stackoverflow.com/a/39608906/6309, or in command-line: stackoverflow.com/a/48415708/6309
Jason Slocomb over 3 years

I had to do the above, visual studio 2019 wouldn't prompt for credentials after removing them with Windows Credentials Manager.
Gultekin over 3 years

Credentials should be asked by a pop-up window when you type "git fetch origin" into the Git Bash command tool.
Enrico about 3 years

"git: 'credential-manager-core' is not a git command. See 'git --help'."
VonC about 3 years

@Enrico You need a recent Git for Windows (github.com/git-for-windows/git/releases) for credential-manager-core to be recognized. Or you need to install github.com/microsoft/Git-Credential-Manager-Core separately on Linux/Mac.
sailfish009 almost 3 years

this whole mass, mingw-git didn't work at all.
Persike about 2 years

This one was the solution to me.