Delete that account's login keychain. I was misinterpreting the output, as I thought that git config regarded the local options. When I run git credential-osxkeychain I see the usage message I'm apparently supposed to. Thanks to for original - very helpful. Everything works like a charm now :. Otherwise you should try opening up keychain.
I'm a n00b in AppleScript but I patched it to work in French. This is still not working in SourceTree 2. Depending on which one comes back showing the credential helper, you can try using the equivalent --unset option: git config --local --unset credential. Click on allow always when popup appears in SourceTree. Enable the Show Passwords option and enter your login password when prompted.
Turns out I store general passwords not associated with websites or things like that so the script ignores them. By default, Git will cache your password for 15 minutes. But I quickly found another problem. I have, as of yet, been unable to find anything documenting this issue. How to Reset Keychain Password after Mac Password Change No matter which method you use to , it won't automatically update the password protecting the account's login keychain.
Make sure to kill any git-credential-osxkeychain process as as well, or see if the issue persists after a reboot. Additionally, when I type git credential-osxkeychain erase or git-credential-osxkeychain erase , the command hangs silently and, as far as I can tell, indefinitely. In the resulting window, enable the Show Password option. Although this worked, I would be prompted twice for my password when attempting to pull or commit, and 'Refresh Remote Status' wasn't working properly. I've followed these instructions; everything seemed to work fine. I tried most of these other fixes, and a bunch off of other websites but nothing worked, so last ditch effort, worked like champ, no more messages. Restart Mac and hold on Command + S to enter single user mode.
The largest pane, to the right, displays the contents of selected category items—for example, all of the items that have a password associated with them. I like hacking and exploring the unix underworld of my mac though, so wrangling with locate is a 'fun' thing for me. Share your login keychain If you have multiple Macs, each one has its own login keychain with its own set of passwords. After that, all operations worked properly from SourceTree, and I am no longer prompted to enter my password. Thx , I was seeing the same thing to, but found this forum: Basically, the importers for 1password 4 are not really complete. I can delete it, and then git will ask for the password again. Don't be tempted to speed up the clicking; at delay 0.
Enter that and click Allow, and the password will be revealed in the Password field. It stores a wide variety of items—including passwords for email, websites, servers, network shares, Wi-Fi networks, and encrypted disk images. Passwords will be listed to the right of each site. If it spouts an error at you, sorry, you'll have to fix the script, something's broken. Once you enter it, you should have access to the same passwords as that master Mac.
You need to delete these securely if you are concerned about the possibility that someone might get your passwords. I hope my answer helps others because I had been struggling with password issues with SourceTree for quite a while and finally figured out the issue. Still, it keeps memorizing my github login details. Log out of your account and then back into it. Probably you are just prompted to do that at startup after Mac admin password reset, such as on Yosemite, or constantly asked to enter the keychain password after Mac login. I was able to successfully import all my keychains using this method.
When you are, enter the password and the keychain will be unlocked. You will be asked this once for every item in your keychain zzz. If you're seeing more than five columns, one of your values contains a rogue comma and you need to fix it manually before you import the file or it won't work. This is a new computer, and the whole system setup is still a work in progress. When the passphrase is provided by the user, this option also specifies whether the passphrase should be stored into the keychain once it has been verified to be correct. I had this same problem recently. Do I have the sudo correct thanks.
I did assign a passphrase to the key pair. Apple doesn't let you change which kind of entry it is. No problems with the following git remote add origin git github. So the last command above would help fix that problem. Landry314 mentioned this above as well.