> -----Original Message-----
> From: Bruce Gough [mailto:bruce_at_ijws.com]
> Sent: Wednesday, 25 June 2008 07:01
> To: users_at_subversion.tigris.org; users_at_tortoisesvn.tigris.org
> Subject: Upgraded Tortoise to 1.50 but still won't ask for
> credentials on commit after it fails with saved authentication
>
> 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!:
>
This seems to me to be doing exactly what you asked it to do?
You authenticated using a read-only account, and
*asked*TortoiseSVN*to*save*authentication*.
You then tried to write, *TortoiseSVN*had*saved*your*credentials* (per
your request), used them, found you didn't have authorisation to write,
and failed with an error.
What happens if you clear the authentication cache and repeat this,
*without* asking TortoiseSVN to save authentication?
Cheers
John
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-25 07:05:28 CEST