I started using Visual Studio Code , and I was trying to save my test project into GitHub , but Visual Studio Code is always asking for my GitHub credentials.
I have installed in my PC GitHub Desktop and also Git . I already ran:
git config --global credential.helper wincred
but still Visual Studio Code is asking for the credentials.
How can I fix this?
Here is my .gitconfig file located in the user profile folfer:
[filter "lfs"]
clean = git-lfs clean %f
smudge = git-lfs smudge %f
required = true
[user]
name = ddieppa
[user]
email = fake@live.com
[credential]
helper = wincred
Here is the popup windows asking for the credentials:
I enter my GitHub credentials in the popup, but still getting this error in the Git output window in Visual Studio Code:
remote: Anonymous access to ddieppa/LineOfBizApp.git denied.
fatal: Authentication failed for 'https://github.com/ddieppa/LineOfBizApp.git/'
After 98 upvotes, I think I need to give a true answer with the explanation.
Why does VS code ask for a password? Because VSCode runs the auto-fetch feature, while git server doesn't have any information to authorize your identity. It happens when:
https
remote url. Yes! This kind of remote will absolutely ask you every time. No exceptions here! (You can do a temporary trick to cache the authorization as the solution below, but this is not recommended.) ssl
remote url, BUT you've not copied your ssh public key onto git server. Use ssh-keygen
to generate your key and copy it to git server. Done! This solution also helps you never retype password on terminal again. See a good instruction by @Fnatical here for the answer.The updated part at the end of this answer doesn't really help you at all. (It actually makes you stagnant in your workflow.) It only stops things happening in VSCode and moves these happenings to the terminal.
Sorry if this bad answer has affected you for a long, long time.
--
I found the solution on VSCode document :
Tip: You should set up a credential helper to avoid getting asked for credentials every time VS Code talks to your Git remotes. If you don't do this, you may want to consider Disabling Autofetch in the ... menu to reduce the number of prompts you get.
So, turn on the credential helper so that Git will save your password in memory for some time. By default, Git will cache your password for 15 minutes.
In Terminal, enter the following:
git config --global credential.helper cache
# Set git to use the credential memory cache
To change the default password cache timeout, enter the following:
git config --global credential.helper 'cache --timeout=3600'
# Set the cache to timeout after 1 hour (setting is in seconds)
I installed VS Code and config same above, but as @ddieppa said, It didn't work for me too. So I tried to find an option in User Setting, and I saw "git.autofetch" = true, now set it's false! VS Code is no longer required to enter password repeatedly again!
In menu, click File / Preferences / User Setting And type these:
Place your settings in this file to overwrite the default settings
{
"git.autofetch": false
}
You should be able to set your credentials like this:
git remote set-url origin https://<USERNAME>:<PASSWORD>@bitbucket.org/path/to/repo.git
You can get the remote url like this:
git config --get remote.origin.url
This has been working for me:
1. Set credential hepler to store $ git config --global credential.helper store
2. then verify if you want:
$ git config --global credential.helper store
Simple example when using git bash quoted from Here (works for current repo only, use --global
for all repos)
$ git config credential.helper store
$ git push http://example.com/repo.git
Username: < type your username >
Password: < type your password >
[several days later]
$ git push http://example.com/repo.git
[your credentials are used automatically]
Will work for VS Code too.
More detailed example and advanced usage here .
Note: Username & Passwords are not encrypted and stored in plain text format so use it on your personal computer only.
The following steps walk you through how to:
**Generating SSH keys without a passphrase is unwise if your work is particularly sensitive.
OS - Fedora 28 | Editor - VS Code v1.23.0 | Repository - Git
Generate SSH keys:
ssh-keygen -t rsa -C "email@goeshere.com"
After completing the above steps, the location of your public key is shown in the terminal window. If the currently logged in user is 'bob' the location of your public key would be /home/bob/.ssh/id_rsa.pub
Copy and import public key to GitHub:
cat /home/bob/.ssh/id_rsa.pub
Copy the whole public key that is now displayed in your terminal window to the clipboard
Confirm the above steps:
ssh -T git@github.com
yes
Hi ! You've successfully authenticated, but GitHub does not provide shell access.
First commit / push without having to enter a username / password: - touch test.txt
git add test.txt
git commit
- opens editor, enter a message and save the file. If vi is your editor, press i
once the file opens, enter a message, press esc, and then enter :x
to save changes.
git push
The only hiccup you may encounter is when you attempt to SSH to GitHub. This link will provide some assistance -
Happy hunting!
All I had to do was to run this command:
git config --global credential.helper wincred
Then I was prompted for password twice.
Next time it worked without prompting me for password.
In general, you can use the built-in credential storage facilities:
git config --global credential.helper store
Or, if you're on Windows, you can use their credential system:
git config --global credential.helper wincred
Or, if you're on MacOS, you can use their credential system:
git config --global credential.helper osxkeychain
The first solution is optimal in most situations.
Try installing " Git Credential Manager For Windows " (and following instructions for setting up the credential manager ).
When required within an app using Git (eg VS Code) it will " magically " open the required dialog for Visual Studio Team Services credential input.
Use ssh instead of http/https.
You will need to set ssh keys on your local machine, upload them to your git server and replace the url form http://
to git://
and you will not need to use passwords anymore.
If you cant use ssh add this to your config:
[credential "https://example.com"]
username = me
documents arehere .
Simply follow those steps and you will set up your ssh key in no time:
Generate a new ssh key (or skip this step if you already have a key)
ssh-keygen -t rsa -C "your@email"
Once you have your key set in home/.ssh
directory (or Users/<your user>.ssh
under windows), open it and copy the content
SSH keys
Add ssh key
And you all set to go :-)
Automatic Git authentication . From the v1.45 Release Notes :
GitHub authentication for GitHub Repositories
VS Code now has automatic GitHub authentication against GitHub repositories. You can now clone, pull, push to and from public and private repositories without configuring any credential manager in your system. Even Git commands invoked in the Integrated Terminal, for example git push, are now automatically authenticated against your GitHub account.
You can disable GitHub authentication with the
git.githubAuthentication
setting. You can also disable the terminal authentication integration with thegit.terminalAuthentication
setting.
For windows 10 : go to control panel/Credential manager/ Windows Credential--> click on the git link, --> edit--> update to new password. That should work
Use an SSH key without a passphrase.
Maybe this is obvious to some (wasn't to me). It also doesn't solve the issue if you absolutely require a passphrase, but this was a decent compromise in my situation on Mac.
After fighting with something like this for a little while, I think I came up with a good solution, especially when having multiple accounts across both GitHub and BitBucket. However for VSCode, it ultimately ended up as start it from a Git Bash terminal so that it inherited the environment variables from the bash session and it knew which ssh-agent to look at.
I realise this is an old post but I still really struggled to find one place to get the info I needed. Plus since 2017, ssh-agent got the ability to prompt you for a passphrase only when you try to access a repo.
I put my findings down here if anyone is interested:
Ubuntu users should simply enter this command in the terminal of vs code:
git config --global credential.helper store
Now, enter one time your username and password and after that, it won't ask you again
Note:
Username & Passwords are not encrypted and stored in plain text format so use them with caution.
But, if your password contains some special characters like @, #, &, * etc, then these characters will be encrypted.
Also, you can find your '.git-credentials' file at home, it's hidden so, make sure to enable hidden files.
Location: ~/.git-credentials
Following thatarticle :
You may just set GIT_SSH env. var.to the Putty's plink.exe program. (Then use the pageant.exe as a auth. agent)
I managed to stop this by carrying out the following steps.
cd "C:\\Program Files\\Git\\mingw64\\libexec\\git-core"
followed by git-credential-manager.exe uninstall
git config --global credential.helper wincred
NOTE: I was using a Personal Access Token as my password.
Solve the issue by following steps.
Uninstalled softwares Vscode and git and reinstalled the same. Changed the git repository clone url from ssh to https.
I had a similar problem in Visual Studio Code.
I solved by changing the remote url to https . (in file .git/config)
[remote "origin"]
url = https://user@server.com/plesk-git/project.git
and also
git config --global credential.helper wincred
pulled again, windows credential popup came out, problems solved.
我通常运行这个简单的命令来将 git 远程 url 从https更改为ssh
git remote set-url origin git@github.com:username/repo-name-here.git
For me I had setup my remote repo with an SSH key but git could not find them because the HOMEDRIVE environment variable was automatically getting set to a network share due to my company's domain policy. Changing that environment variable in my shell prior to launching code .
caused VSCode to inherit the correct environment variable and viola no more connection errors in the git output window.
Now I just have to figure out how to override the domain policy so HOMEDRIVE is always pointing to my local c:\\users\\marvhen
directory which is the default location for the .ssh
directory.
I solved a similar problem in a simple way:
git pull origin master
. Replace 'origin' with your Remote nameThat's all. I Solved the problem
apart from adding the ssh config entries above
if windows
Set-Service ssh-agent -StartupType Automatic
in powershell now the vs code should not prompt...
for windows 10 press windows key type cred and you should see "Credential Manager" in Control Panel click to open and then remove the related cached credentials then try again, it will ask user id password key in the correct password and you'll be good.
Happened with me when I changed my network password
You can refer this link for setup a Git Credential
You can run the following command to save your git credentials. You no need to enter username and password every git command run. (Its for Windows )
git config --global credential.helper wincred
For Mac / Linux click on this link for How to save Git credentials
In case you are on Windows PC Then answer you are looking for!
Install Git for Windows
That's it!
Opposite problem but related:
In my case I was struggling with vscode integrated terminal not forgetting the entered password even though cache helper timeout had expired already.
External terminal sessions were working fine though.
Found there happens to be an option in vscode which let you set an optional cache on top of the actual git plugin, which wasn't allowing the expected behaviour to occur.
Once checked, my passwords were being forgotten on cache timeout, so I could start jumping from personal to work accounts without efforts :)
On Linux, vscode 1.58.2
Ran on vscode ubuntu-focal 自动解决了定期询问凭据的问题
git config --global credential.helper store
your user to open visual studio code must same with your user to execute git command, then in a terminal, you can run command
git config --global credential.helper store
then run
git pull
in the next action push or pull you will not see asking for git credentials
(This answer is not specific to GitHub, instead I was using BitBucket, but it may work in GitHub too, because the concept is the same)
In my case I was using a Bitbucket app password and it always asked me to authenticate.
Stopping automatic fetch doesn't solve the problem because I pull and push several times in a day, and entering the app password everytime is just bad.
Furtermore, I would need to store the app password somewhere unsafe, which is also the reason that I don't want to use credential.helper store
, that stores the password in plaintext, and instead use credential.helper wincred
, which is encrypted.
When the dialog prompted me, instead of using the app password, I asked to sign-in using the browser, which worked, for reasons that are beyond my understanding. Now it doesn't ask for credentials anymore (I had to change my default browser temporarily, because the bitbucket account I use for work is not in my default browser, and the dialog try to authenticate using the default browser).
This works for me. you only need to type in PAT once. git config --global credential.helper wincred
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.