On 1/25/07, Andrew Lentvorski <bsder@allcaps.org> wrote:
>
> Am I doing something wrong here? Names changed to protect the innocent.
> I'll try to get them consistent though.
>
> System: Eclipse 3.2.1 on Windows with Java 1.5. Subclipse 1.1.9 (same
> problem in 1.0.4 though) using SVNKit. Both repositories known good as
> they can be accessed by command line SVN and TortoiseSVN. They can also
> be accessed through subclipse (but not together, see below). Server SVN
> is version 1.4.2 (r22196) running on Solaris.
>
>
> Open SVN Repository Perspective.
> New -> Repository Location
> Add SVN Repository Dialog
> URL: svn+ssh://acct01@server.bigu.edu/home/svn/acct01/svnrepos
>
> Enter SSH Credentials Dialog:
> Repository: svn+ssh://server.bigu.edu
> Username: acct01
>
> Use password authentication-Correct
> Password: ********
> Save Information: not checked
>
> Ok.
>
> Enter SVN Author Name Dialog <- Huh?!?! WTF?!?!
> Repository: svn+ssh://server.bigu.edu
> Author Name: acct01
> Save author name not checked.
>
> The author name is *required* to match the Username or it will fail.
>
> Ok. Hunky dory. The repository is fine.
>
> Next up:
> New -> Repository Location
> Add SVN Repository Dialog
> URL: svn+ssh://acct00@server.bigu.edu/home/svn/acct00/svnrepos
> Finish
>
> KABLAM!!!
>
> Error validating location:
> "org.tigris.subversion.javahl.ClientException: svn: Can't open file
> '/home/svn/acct00/svnrepos/format': Permission denied
>
> If, however, I delete the .keyring and reverse the order of add (ie. add
> acct00 first rather than acct01), then acct01 will blow up instead.
>
>
> What is going on? Why am I being asked for a redundant credential that
> the system already has (Author Name) which can only hose me up? The
> system appears to be caching the credentials from the first login and
> applying that to my second repository login (I never even get an SSH
> credentials dialog for the second repository). Why?
>
> How do I work around this?
The SVN Author dialog is something that SVNKit adds (I am not crazy about it
either). I guess the reason is that it is not entirely uncommon to login to
an SSH server with different credentials than you want for the author name
in SVN? I think with OpenSSH there is a switch for this, and so SVNKit
needs to do it with a GUI option.
The caching problem sounds like an issue with SVNKit. Try emailing this to
support@svnkit.com.
If the command line and TortoiseSVN are working for you, then maybe you
should just use JavaHL. That would use the same SSH client you configured
for those tools. If you use TortoisePlink, you will just get prompted for
credentials by it.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Thu Jan 25 16:43:32 2007