I think Versions could probably be a bit smarter about failed authentications on the same server, but given the variety of ways hostnames can be written, this is a difficult problem. (Not trying to make excuses, just sayin'...)
One workaround is to manually change the passwords in Keychain Access (in Applications > Utilities) while Versions is not running. Type "SVN: " (note the trailing space) in the search field in the toolbar to filter the password items which Versions uses for authentication. I've found that the svn command-line tool and Xcode each have different formats for naming Keychain items, so you may see multiples (when not filtered as above) if you've accessed repositories via other methods. Hope that helps, - Quinn On Jul 20, 2010, at 3:13 AM, Mat wrote: > At my office we have a single password for most of our systems and I > am allowed three authentication attempts before my password is locked. > This includes attempts to connect to the Subversion repository. > Versions causes a problem here as, if I change my global password, > starting Versions will cause it to automatically make requests to the > SVN server to count the remote changes with its out-of-date stored > copy of my credentials. If I have three or more bookmarks, this will > lock me out. > > Once locked out, I can't change my credentials in Versions as it > insists on attempting to authenticate before storing them. > > Is there any way to minimise the number of connections Versions makes > with the server? > > Cheers, > > Mat
smime.p7s
Description: S/MIME cryptographic signature
