I'm using git-svn with a couple of work projects and I've noticed that for just about every action I take, I get prompted for my Svn password. For some actions, I get prompted multiple times (presumably b/c there are several actions going on behind the scenes). For example, when cloning a repository, I'm prompted 5 times before the cloning actually begins.
Projects for which I'm using Svn directly don't do this. Is this expected? Is there anything I can do to cache my credentials?
Thanks.
On Windows, the Subversion client stores passwords in the %APPDATA%/Subversion/auth/ directory.
On UNIX/Linux, there are no standard system encryption facilities, so the password is stored as text in ~/. subversion/auth/.
I ended up having to delete the auth directory all together and allow Subversion to rebuild it for me. Nothing else seemed to work. For anyone who doesn't know, the auth directory is in ~/.subversion (Mac/Linux).
I had a similar problem in Sierra. svn
worked fine with the stored credential, but git svn
would not use the stored credential, and kept prompting for it to be re-entered.
The solution for me was to delete the stored key in keychain, and then use git svn
before any other program. If git svn
was the program to store the password in keychain, then the permissions were properly set. Once git svn
had been used to create the entry in keychain, then normal svn
could be used, and allowed to access the key created by git svn
, at this point they would both use the repository without any issues, and without me being prompted for the password all the time.
If any other program set the password in keychain, then that program had no problems, but git svn
would not be given permission.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With