{c}
-- On Thu, Jan 26, 2012 at 4:47 PM, Chooch Schubert <choochus@gmail.com> wrote:
This tutorial from IBM may help you. It is listed as current for Cake 1.3.4 and they are working to update it for 2.0. Even given the differences, it might give you some code examples that you can manipulate to get what you want.{c}
On Wed, Jan 25, 2012 at 5:18 PM, Brian <brian.d.smith@gmail.com> wrote:I'm working on the authorization system for my web app. I began
researching various ACL guides back during 1.3, but never found one
that really clicked in my head. I've read the Cookbook tutorials, the
Permissionable behavior, SuperAuth on github, etc trying to find a
record-level auth solution that I understand well.
In the end I left the app to behave like the tutorial (e.g. Aragorn
can have Read access to all Weapons, but there's no way to grant him
access just to a single Weapon like a Sword). This was a compromise,
though, and what I really need is a way to grant permissions on
specific instances of a Model.
Now that CakePHP 2.0 has been released and I've upgraded my app, I'd
like to try tackling this problem again. Are there any resources that
address this kind of ACL for 2.0? Is this already possible and I just
haven't realized it yet?
Thanks for your help.
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
No comments:
Post a Comment