Does Git-Svn Store Svn Passwords?

Maybe a stupid idea, but I found git-svn was re-prompting for password even after resetting the keychain entry. So I changed the Access Control for that item so "all applications" can access it. Seems to work?

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.

You should ask SVN to cache your credentials:

# $ svn update --username 'user2' --password 'password'
# [email protected]'s password:

However, as mentionned in the SO question Subversion ignoring “—password” and “—username” options, check what exactly is prompting you for a password.