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

Re: 'owner' in dav LOCK request. (Julian Reschke, you out there?)

From: Greg Stein <gstein_at_lyra.org>
Date: 2004-12-01 23:20:55 CET

On Wed, Dec 01, 2004 at 10:28:00PM +0100, Julian Reschke wrote:
> Ben Collins-Sussman wrote:
> >I'm worried, because this doesn't mesh with Subversion's locking
> >semantics at all. To make use of a lock, Subversion requires *both*
> >the lock-token (which is publically available) AND that the user be
> >authenticated as the lock's owner.
> That's fine. The DAV:owner element in the lock request is just
> client-controlled metadata. Servers may associate locks with
> authenticated users, but in this case, the user information needs to be
> obtained from the HTTP authentication details, not the LOCK request body.

Ben: this is the key part. Pick up the lock owner from r->user, not
the owner element. IOW, the user that authenticated with the server.

> >If WebDAV doesn't have this same double-authentication requirement,
> >then I don't understand how locks are supposed to be enforced:
> >
> > User A authenticates, does a LOCK, gets a token.
> > User B authenticates, does a PROPFIND, discovers the token.
> > User B then does a PUT using the token.

B needs to authenticate as A to allow the PUT. Even though B has the
token, that is not enough. B needs both the token, and to authenticate
as A.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 1 23:19:40 2004

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

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