"Alexander Kitaev" <alex@tmate.org> wrote on 01/13/2006 02:22:25 AM:
> JavaSVN does not suppport SSPI authentication at the moment (only Basic
and
> Digest types are supported for http, and client cert authentication for
SSL
> over http). So, you should concentrate on trying it with JavaHL - in
case
> command line version works, JavaHL should work as well. At least there
are
> no obvious reasons for it not to work properly...
Support for SSPI in Subversion is based in the Neon library, which added
support for SSPI in version 0.25.1 (with the current version being
0.25.4). Developers building Subversion 1.3.0, specifically TortoiseSVN
which is obviously heavily used by Windows Subversion users where this
applies, have discovered massive bugs in the SSPI support. Endless loops,
enormous increases in bandwidth usage, incorrect authentication etc...
Therefore, the JavaHL that I ship with the Windows version of Subclipse is
compiled with the SSPI support in Neon turned off. TortoiseSVN has had to
make the same change. When/if the problems are resolved in an official
Neon release, we will look into enabling it in our build.
That being said, if neither JavaSVN nor JavaHL are falling back to basic
auth I would think you have a server misconfiguration of some sort.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri Jan 13 14:32:17 2006