Re: On backporting r21531 to 1.4.x.

Joseph Galbraith wrote:

> In my humble opinion, which counts for nothing, I think
> where we need to be eventually is having subversion
> tell SSPI what user it wants to authenticate as.

I don't think that's possible. SSPI uses the anonymous user (the GUEST
account) or the currently logged on windows user. If it's possible to
specify the user it authenticates with, where would it get the password
for it? It only can do that by using the already logged on user and the
password used to log the user on to the workstation.

> I'm 90% certain SSPI gives this level of control... of
> course, if I had to guess, I'd guess neon doesn't give
> this level of control :-(

I'm 90% certain that SSPI can't give that level of control :)

> Right now, the main issue we are running into is that
> SSPI succeeded with a user like GUEST, and we wish
> it hadn't.
>
> I suspect it is entirely possible that we will run into
> cases where SSPI succeeds with user x, but we wish it
> had succeeded with user y (I don't think it is common
> to have multiple user credentials available but I don't
> think it is impossible either.)

For those cases, you could provide the command line params
--username myname --password mypassword

If those are present, then Subversion must tell neon to not authenticate
with SSPI in the first place but only use basic authentication.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org