[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Irritating authentication problem - I can't *stop* svn authenticating as 'administrator'

From: Jonathan Ashley <jonathan.ashley_at_praxis-his.com>
Date: Mon, 11 Feb 2008 08:51:42 +0000

> > My setup uses an Apache server running Apache 2.2.4 / SVN
> 1.4.3 with
> > SSPI authentication. Access via https.
> >
> > I normally use the Tortoise client, which works great. I'm
> sure that
> > the command line client used to work great, but now it doesn't. The
> > problem is that whenever I use the command line client to make a
> > commit, the svn:author property of the revision becomes set
> to 'administrator'
> > instead of my login name.
>
>
> This can happen if you have explicitly mapped drives or
> printers or some other resource on the server machine with
> those credentials (ie, you accessed a folder or printer or
> something and told Windows to 'save' those credentials so it
> can magically reconnect anytime you
> access that resource). If you have already established an
> authenticated connection to that machine, then SSPI
> automtaically uses those credentials.
>
> Get rid of mapped drives, printers, etc. on that server and try again.
> The 'net use' command may be helpful in identifying and
> deleting those kinds of connections.

That was a great idea, and I was sure you were right, because I
do have drive shares mapped in both directions.

Sadly, after deleting all such shares on both machines, logging out
on both machines (and back in on my client machine), the problem
is still there. Even tried pointing at a local non-existent config
directory again.

Then I had the bright idea of capturing the traffic with Ethereal -
see what authentication information gets sent. Oops, not so bright,
it's SSL-encrypted. So I did an 'svn switch --relocate' on the
working copy to change it to http. Immediately, I got prompted for
my password! I did a commit, and it prompted again, and went in
with the right user name.

So I switched back to https. It went back to automatically going
in as 'administrator'. Grrrr!

This makes me wonder if the problem is something to do with the
way the SSL layer is caching authentication information? I did a
test with Tortoise too, and found it behaves exactly the same. I
think I must have used an http-based working copy before - sorry
if I misled.

Thanks very much for your suggestion anyway. I will keep plugging
away at it, and if I ever find the solution will post it here...

regards,

--
Jon Ashley
This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, disclosure, copying or distribution or any action taken or omitted to be taken in reliance on it is strictly prohibited. If you have received this email in error please contact the sender. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Praxis. 
Although this email and any attachments are believed to be free of any virus or other defect, no responsibility is accepted by Praxis or any of its associated companies for any loss or damage arising in any way from the receipt or use thereof. The IT Department at Praxis can be contacted at it.support_at_praxis-his.com.
Praxis High Integrity Systems Ltd:
Company Number: 3302507, registered in England and Wales
Registered Address: 20 Manvers Street, Bath. BA1 1PX
VAT Registered in Great Britain: 682635707
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-11 09:52:11 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.