A question about path-based authorization via the HTTP's LDAP protocol

[Victor Gong <Vi...@phoenix.com>]

Hi, all
Could somebody help me?
The question confusing me is the subversion 1.5's path-based authorization via the HTTP's LDAP protocol.
I want some trunks in the repositories can read and write for some ones, but only read for others.

I noticed there is a segment which describes a useful feature to the access file syntax:username aliases, Do you know how to realize my wish:
Subversion 1.5 brings another useful feature to the access file syntax: username aliases.
Some authentication systems expect and carry relatively short usernames of the sorts
we've been describing here-harry, sally, joe, and so on. But other authentication systems-
such as those which use LDAP stores or SSL client certificates-may carry much
more complex usernames. For example, Harry's username in an LDAP-protected system
might be CN=Harold Hacker,OU=Engineers,DC=red-bean,DC=com. With usernames
like that, the access file can become quite bloated with long or obscure usernames
that are easy to mistype. Fortunately, username aliases allow you to have to type the correct
complex username only once, in a statement which assigns to it a more easily digestable
alias.
[aliases]
harry = CN=Harold Hacker,OU=Engineers,DC=red-bean,DC=com
sally = CN=Sally Swatterbug,OU=Engineers,DC=red-bean,DC=com
joe = CN=Gerald I. Joseph,OU=Engineers,DC=red-bean,DC=com
...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org