Ben, can you elaborate a bit on how you structured your DB schema for ACLs? I'm facing this problem right now (need ACLs at both app level and database level), and I would appreciate understanding a little more about the intent of the Acegi design in that respect.  (Apologies for resurrecting an old thread).

Ben wrote [Jan 21, 2006]:
> I've also used views at a RDBMS level instead of relying on Acegi
> Security to ACL filter very large tables. However, the underlaying
> tables which the views used were structured so that I could also use
> them with an Acegi Security BasicAclDao implementation. This let me use
> the RDBMS where appropriate (large tables) and Acegi Security/Java for
> the rest (including managing the ACL entries in the table).

David Berkowicz wrote [Jan 22, 2006]:
> I was think of using some type of object
> hierachy so that I could exploit inheritence at least in the ACL
> table. A more probable and managable alternative, I think, will be to
> use a better database schema.

Ben wrote [Jan 22, 2006]:
> For large applications we expect people will use a
> schema optimised for their needs, or an existing domain object which
> offers a business-centric view of permissioning data.

Reply via email to