"Steve Dwire" <sdwire@pcsigroup.com> writes:
> I'm connecting via http: to an Apache server. We just switched from
> anonymous access to SSPI authentication. If I connect to the repository
> using Internet Explorer, it prompts me for my username and password, and
> then I can successfully connect and browse using http://. So, it appears
> that the server side is correctly set up.
>
> Whenever I run any svn command against the repository, though, I simply
> get an "Authorization failed" error. I do not get any prompt for
> username/password. If I add the --username DOMAIN\username
> --password=****** arguments to the command line, it makes no difference.
> When using TortoiseSVN, I get an immediate authorization failure as
> well.
I honestly have no idea what SSPI authentication is. Is it
fundamentally different than an HTTP Basic Auth challenge?
This might just be a limitation in neon, which is the HTTP client
library that the svn client uses. I know that neon understands Basic
Auth challenges, and can handle client/server certificate challenges,
but maybe not SSPI?
Someone correct me, please.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 24 00:48:03 2003