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

Re: Upgraded Tortoise to 1.50 but still won't ask for credentials on commit after it fails with saved authentication

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 24 Jun 2008 21:08:22 +0200

Bruce Gough wrote:
> I upgraded Tortoise from 1.4.8 to 1.5.0 but it had no effect on this
> problem:
> I do an update, using a read-only account and check "save
> authentication". It does the update. I can view logs, do diffs etc.
> When I commit, I expect it to fail because the account is read only, and
> to ask me for credentials to do the commit. But it just gives an error
> and gives up (see below)
> Command: Commit Error: Commit failed (details follow): Error: Server
> sent unexpected return value (403 Forbidden) in response to MKACTIVITY
> Error: request for
> '/svn/hksk/!svn/act/6c3af0bd-8c47-2b43-90a9-e319737a042a' Finished!:

You've configured your server wrong. If you get an 403, then that means
that the author/password Subversion provided is good, but that user
doesn't have access, i.e., the *authentication* succeeded, but the
*authorization* was successful.
Either allow your user to have write access, or reject that users
password the first time for a commit (i.e., when committing, the user
with read access should be not known at all to the server so it returns
a 401 instead of an 403 later).


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net

Received on 2008-06-24 21:08:42 CEST

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

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