Hi Will, We have a variety of requirements in this direction.
One way to handle it at the page level is via Templates - in our case we can assign a certain template to the protected pages, and handle the security checks in the template-model's execute() method. I'm not 100% happy with this from a security standpoint, but in this case our requirement wasn't for high security, just a basic solution, so it's probably ok. Obviously, it would be simple to configure the security settings in the page properties in this kind of setup. Regards from Vienna, Richard (iPhone) On 13.03.2011, at 20:22, "Will Scheidegger" <[email protected]> wrote: > > Dear Magnolians > > We have the request to restrict access to certain pages for certain groups > (instead of whole branches). Now this of course could be done with the > regular ACL (editing the roles for every single page which should be > protected). But this would undoubtedly lead to a configuration nightmare. > > Has anyone come up with a better solution yet? The goal would be to select > the group which may access the page directly in the page properties. > - Should we create a new save handler which then adapts the ACLs accordingly? > - Or should we create a whole new access restriction mechanism? > > Thanks for any input! > -will > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
