I have a similar problem that only seems to happen when using JavaHL. If
JavaSVN is used, the problem disappears.
In my case, tho, I use https and the Repository uses LDAP to
authenticate me with the corporate network.
When you mention:
> When using svn+ssh:// URLs to access a repository, remember
that it's the ssh program prompting for authentication, and not the svn
client program. That means there's no automatic password caching going
on (see the section called "Client Credentials Caching"). The Subversion
client often makes multiple connections to the repository, though users
don't normally notice this due to the password caching feature. When
using svn+ssh:// URLs, however, users may be annoyed by ssh repeatedly
asking for a password for every outbound connection. The solution is to
use a separate SSH password-caching tool like ssh-agent on a Unix-like
system, or pageant on Windows.
I don't see why the password has to be cached in an underlying
middleware, and it would be nice to avoid this kind of problem on a
basic install.
Best regards,
Felipe
Received on Tue Oct 24 16:53:52 2006