By default JavaSVN uses persistent ssh connection, once you're connected to
the certain host (with the same user name) this connection will be resued.
Also ssh credentials are stored per "realm" that is "host:port" in case of
ssh, so you could not have two different credentials for the same host (the
same is for other protocols, credentials storage key only includes "realm",
not user name and native subversion works the same way).
I will think on providing more complicated credentials caching scheme, but
it will not be included into 1.0 version, as it is more or less major
modification.
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Werner Punz
> Sent: Friday, October 28, 2005 10:39
> To: users@subclipse.tigris.org
> Subject: Re: Subclipse SSH User Name bug
>
> Werner Punz wrote:
> > Hi9 alex just installed your new jar, and restarted Eclipse with
> > clean, private key auth, which did not used to work with the old
> > version works now again, but the user name problem still is there.
> > There must be another bug.
> >
> > Werner
> >
> >
> > Alexander Kitaev wrote:
> >
>
> Alex another bug, I have two repos on the same machine I try
> to connect with different users and pubkey auth, only the
> first one is accepted the second one ignored, although both
> work as expected, I am not sure if this is a bug in subclipse
> or javasvn, I cannot verify it on javahl.
>
> Werner
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Sat Oct 29 02:36:02 2005