RE: How to allow anonymous access, but not everyone access in path-based authorization?

Hi,

Didier Trosset wrote:
> I have a subversion server running with apache. It authenticates
> users using LDAP configuration and uses SVN path-based
> authorizations to limit user access to certain repositories.
> This works perfectly.
>
> Now, I have a service I want to setup (rietveld, for code reviews)
> that needs to have an anonymous access to the repository.
> [... snip ...]
> This did not work until I add an additional line "* = r" in the
> authorization file to allow read access to all users.
>
> For instance, before I add the authorization from a specific IP,
> all users were authenticated, and thus had a name. Now, some
> accesses are done without a user name! I found the |"-|" user
> name in the apache log files, but the line "|- = r"| does not work,
> neither do |"anonymous = r"|. I'd like not to allow read access to
> everyone in SVN authorization. How can I do this?

Subversion's authz files support "$anonymous" to refer to anonymous
users. (And "$authenticated" to refer to authenticated users).

Kind regards,

Jon

--
Please direct all replies to the mailing list
**********************************************************************
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Cabot Communications Ltd.
If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone.
Cabot Communications Limited
Verona House, Filwood Road, Bristol BS16 3RY, UK
+44 (0) 1179584232
Co. Registered in England number 02817269
Please contact the sender if you believe you have received this email in error.
**********************************************************************
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________