Changing the user for authentication

Hello.

I'm building a setup to manage our servers configuration. All the
configuration are checked out in a central place, and scripts/symlink/
hardlink are used to "propagate" changes on the system. This central
place is obviouly protected so that only root, or a member of the good
group, can access it. This copy is checked out as a special user that
only has reading privileges.

But here is my problem: I want that when a commit has to be done, it is
done as the user of the admin that is doing the change. Since the copy
was checked out as the "reader" user, I must re-authenticate. It goes
like this:

- - - - 8<- - - -
[_Checkout]# svn status
M README
[_Checkout]# svn commit -m "A bogus update"
Sending README
Authentication realm: <http://SERVER:80> Authorisation - developpement
Password for 'reader':
Authentication realm: <http://SERVER:80> Authorisation - developpement
Username: myuser
Password for 'myuser':
Transmitting file data .svn: Commit failed (details follow):
svn: PUT of '/adm/!svn/wrk/4137c712-2df4-0310-a645-c8acb0fe8a44/README':
501 Method Not Implemented (http://SERVER)
[_Checkout]#
- - - - 8<- - - -

In the server log, I have:
- - - - 8<- - - -
[Thu Apr 07 14:42:37 2005] [error] [client 192.168.66.89] user reader:
authentication failure for "/adm/!svn/ver/14/README": Password Mismatch
[Thu Apr 07 14:42:46 2005] [error] [client 192.168.66.89] Could not
fetch resource information. [501, #0]
[Thu Apr 07 14:42:46 2005] [error] [client 192.168.66.89] (84)Invalid or
incomplete multibyte or wide character: Multi-author commits not
supported. [501, #0]
- - - - 8<- - - -

There is not really any trace about my authentication request with
"myuser" : it seems to try to use the two users at the same time?

I've found this message in the archive:

http://svn.haxx.se/users/archive-2004-12/0035.shtml

That describe exactly what's going on here; the work-around of adding
--username myuser work.

I was first running with version 1.1.1 : I've upgrade both the server
and the client (it's on the same machine) to 1.1.4, and the probleme is
still there. I also searched the Issue database, but did not found
anything related to this.

Is this a bug, a a misunderstanding of something on my part?

-- 
Benoit Caron
Administrateur système
Canoe inc.
----
This message has been brought to you by the language C and
the number F.