michel.brabants@euphonynet.be wrote:
> Hello,
>
> I checked on roadmap-site of subversiona nd can't seem to find any plans
> to provide a kind of plugin-system to provide additional methods of
> authorization . This is a point in which subversion is lacking to my
> opinion. I could use apache to direct this, but I don't find this a good
> solution. If I would use apache to limit access, those permissions
> wouldn't be applied when ssh+svn would be used (which isn't the case).
> However, we use trac, which also only shows the content that a user may
> view, based on the authz-file. So, using apache for authorization would
> allow users to view the content through the trac-browse-feature.
> I could synchronize the files manually or using hooks to update the
> authz-file, but I'm not sure if that covers everything (have to check) and
> a plugin-system of a direct ldap-implentation would be better.
>
> So, are there any plans to implement ldap-authorization and is there a
> planning?
>
This has been discussed before, but there's no real set of requirements
let alone a design of how that will look like. Feel free to step in :)
Some time ago there was a patch on the dev list which might or might not
do what you want:
http://svn.haxx.se/dev/archive-2006-07/0107.shtml
Lieven.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 19 20:52:15 2006