Explain this a little further because I am a little confused. What do you intend to happen when a directive like:
require group ldap:foo dbm:bar bash is issued? The problem here is the confusion as to which module is handling 'group'. In order for this to work, every authorization type needs to be unique which probably means that they need to be prefixed with the authorization handler name require file-group somefilegroup require ldap-group cn=someldapgroup,o=whatever require dbm-group somedbmgroup Then as we discussed a few weeks back, Satisfy <any|all> would have to be refactored to deal with authorization types rather than just the basic access control. Or am I missing something?? Brad >>> On 10/25/2005 at 9:47:31 am, in message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > > Or not... why not > > require group ldap:foo dbm:bar bash > > where bash would be a match against any provider, while foo would be > specific > to ldap, and bar would be specific to dbm?
