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

Authentication/authorization issues

From: Gino Marckx <dev_at_xodiac.be>
Date: 2005-04-29 11:27:25 CEST

Hi there,

1. I have a mixed authentication and anonymous access setup for my
Subversion installation and wanted to do the following for the test
repository (which everybody can use to fool around with and get acquainted
with Subversion in our company).
So it is obvious that everybody has got write access, so the following
line is added to the [test:/] section of my subversion access policy file:

  * = rw

Now, for obvious reasons, locking cannot be used. So I added the
following line to the section for the developers to be able to test
locking when they wanted to:

  @developers = rw

Apparently this does not work. Apache always seems to take the anonymous
account in this case, and I get the message:

  svn: Lock request failed: 401 Authorization Required

Is there any way to do what I want to do? Because I don't want to specify
all non-developer users in the subversion access policy file...

2. Another thing. I think it would be very useful to be able to refer to
user groups when specifying other users. E.g. like in the following
example:

  admins = admin1, admin2
  developers = @admins, developer1, developer2, ...

3. Currently it is not possible to automatically secure (write lock) all
tags. If it would be possible to specify something like:

  [test:/tags/*]
  * = r

Then this would automatically be the case.

Regards,
Gino.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 29 11:28:26 2005

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.