Purple Streak wrote:
> I've managed to set up an Apache Server with SSPI authentication and
> it's all working well so far except.... at first I had commented out the
> #SSPIPerRequestAuth on
> as I didn't really know what it was, and with it like that TortoiseSVN
> worked fine, never asking for credentials and using the logged in
> windows user to authenticate. Then I looked it up and found this post:
> So obviously I want to have SSPIPerRequestAuth on, but as soon as I did
> I also had the users come to me and say Tortoise is now asking for the
> I've just told them for now to user their normal windows acct. and
> password and to check the "save authentication" button - and that works
> just fine, but like the other post I would rather it just worked without
> have to enter and save the credentials.
> Is this an issue with Tortoise or something in mod_sspi_auth.
> (apologies - it looked like this mail got sent prematurely somehow...
> quite new to how gmail works!)
Subversion doesn't really know about the authentication, it uses other
modules to do that job. For SSPI authentication, it's the neon library
that does the job.
But neon does the authentication according to the data it gets from the
server. And simply activating SSPIPerRequestAuth should not change the
authentication, at least not as far as I know.
So I would suspect that this is a problem of the mod_auth_sspi module.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-09-05 22:14:15 CEST