svnproxy 1.3.0 RC1 can\'t connect using SSPI

( SVNSCC , Delphi, 1.3.0 RC1, WIN 2000/XP )

Type: Public Status:Closed Created: 09 Mar 06 03:00 Updated: 13 Mar 06 03:00

--> Igor Pushkov (admin) at 13 Mar 06 03:00 writes

We make some researching about this issue and found that this beahvior
seems not to be specific only for SVNCOM/plug-in. Some users claims that
even they specify --username and --password for command line client it
ignores this. I.e. when authentication with current credentials is fine
then it ignores other ways to specify it.
I am not think it is not good idea make this behavior diffrent from one
client to another. So, can you please check that either TortoiseSVN or
svn.exe (with --username --password) work as expected?
Unfortunatly we does not use Windows Domain (our servers are unixes) so it
is hard to check this here.
Thanks is advance.

--> G.J. Doornink (user) at 11 Mar 06 03:00 writes

Thanks for your quick reply.

Unfortunately the SSPI authentication in RC3 doesn't allways seem to use
the entered user id on the 'Select SVNURL, module and local path' form.
Instead, when trying to connect to the subversion repository from a client
machine 'within' the same domain as the machine hosting the subversion
repository, the actual used user id as reported by the Apache access logs
is different from the logged on user id of the client machine. The user id
in the Apache logs is the same one with which a network drive was mapped on
the client machine to a share on the machine hosting the subversion
repository.

When trying to connect from a client machine 'outside' the domain through a
VPN connection, svnproxy 'does' use the supplied user id to connect to the
machine hosting the subversion repository. In this case all goes well.

This automatic selecting of the user id by neon is something I would turn
off immediately if I could. Especially since I don't allways connect to the
repository using the logon user id of the client machine. For example when
setting up a working copy for a co-worker.

In other words if you could add a configuration option to turn off the
automatic user id selection by Neon you would make my day :)

Kind regards,

--> Igor Pushkov (admin) at 10 Mar 06 03:00 writes

Latest neon 2.5.5 now in RC3. Please check and reopen if it will not work.

--> G.J. Doornink (user) at 09 Mar 06 03:00 writes

svnproxy 1.3.0 RC1 can\'t connect to a subversion repository served by
Apache 2.0.54 hosted on a Windows 2002 workstation that is part of a domain
from a windows 2000 workstation that is not part of that same domain (e.g.
through a VPN connection)

This looks like the same problem TortoiseSVN 1.3.X also had and is caused
by the new automatic sspi authentication performed by the new Neon version
as used by Subersion/TortoiseSVN 1.3.X

I believe TortoiseSVN has 'fixed' this by patching the used Neon version.

Would it be possible to apply the same 'patch' as TortoiseSVN has to
svnproxy, since this problem is unfortunately preventing me from using
svnproxy 1.3.0 RC1.

See also:
http://tortoisesvn.tigris.org/
http://svn.haxx.se/tsvn/, search for the words 'svn neon domain' (without
the quotes)

Kind regards,

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

svnproxy 1.3.0 RC1 can\'t connect using SSPI