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

Re: [Fwd: svn: Lock request failed: 401 Authorization Required]

From: Jeb <jeb.beasley_at_penske.com>
Date: 2006-06-26 17:04:51 CEST

We are using Apache authentication/authorization to limit access, not

Up until we got into this lock issue, this kind of authorization scheme
is working well. The problem surfaced when users set the needs-lock
property on files.

As I understand, the mod_authz_svn mechanism does not do any pattern
matching, and out tests indicate that if we have a rule for
that is does not match

We have branches like dev_gh, dev_phase2, dev_pl and based on the
parent project control access to group members for that group.

When I request a lock, the apache logs show several authenticated
propfinds, and then a LOCK request without the authentication token.
(Log snippet attached to previous message)


Erik Huelsmann wrote:

> On 6/26/06, Jeb <jeb.beasley@penske.com> wrote:
>> Erik Huelsmann wrote:
>> >> httpd directives
>> >
>> # match urls for the 'ecomm' reposoitory, skip svn specific stuff,
>> webprojects group ( company conventions
>> # to separate functional development groups), dev.* developers use dev
>> branches
> Uhh. No, Subversion authentication/authorization doesn't work that
> way: you need to authorise at a repository level. DAV uses an internal
> URL scheme which doesn't match the URLs you match on here.
> You *need* to use mod_authz_svn if you want path-based access in your
> repository.
> bye,
> Erik.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 26 17:06:53 2006

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.