Hello! It took me a while, but I was finally able to understand and implement a good system for the Auth component. This tutorial helped to explain what I was reading in book.cakephp.org:
http://www.jbcrawford.net/archives/45 In the near future I will possibly be upgrading what I have done to ACL. This tutorial looked like the best for my needs: http://brolly.ca/blog/web-development/cakephp-acl-tutorial/ For my application (groups, user, distributors, dealers, technicians, etc.) I may not need ACL just yet. With model associations I have been able to limit access to just the rows for a logged in distributor, for example. That yields the dealers associated with that distributor via choices set in "recursive" on the find(all) and paginate functions. I am going for simple right now, and may expand the application to ACL after my base knowledge is more solid. Hopefully this helps a bit. Keep on it! You can do it! On Aug 9, 12:24 am, delocalizer <[email protected]> wrote: > Hi Miguel > Remember that Acl and Auth are quite different things - Acl only > establishes the *rules* for what can control what, Auth does the > actual authentication (permits or denies). Having said that, Auth is > designed to work with Acl, and it can do that in a couple of different > ways - if you set the authorize property to 'actions' (easiest to do > this in your AppController::beforeFilter, so it's set for all your > controllers) then Auth will expect to validate against aros_acos table > where acos are aliases for controllers/actions. You don't need to use > mapActions if you're doing that. The example in the manual (http:// > book.cakephp.org/view/641/Simple-Acl-controlled-Application) is > excellent. If you set authorize to 'crud' then it expects that the > acos are database objects. > > On Aug 8, 5:05 am, mig_akira <[email protected]> wrote: > > > Hello everyone! > > > I've been trying to make a simple site using Acl/Auth. Everything is going > > fine, except that I don't quite understand the differences between the 4 > > kinds of 'authorizes', nor how to implement them. > > > For example, I don't understand how can I use the AclComponent::check() to > > authenticate the user when using authorize->'actions'. The same with > > authorize->'crud'. Where do I put the mapAction? In appController, or in > > every controller? What does it exactly do? > > > Sorry, but every blog I found about this say that they don't really know how > > to use those, and the manual is very briefly about this! > > > Thanks!!! > > > (By the way, I'm using authorize->'actions' and I keep getting > > [code] > > DbAcl::check() - Failed ARO/ACO node lookup in permissions check. Node > > references: > > Aro: Array > > ( > > [User] => Array > > ( > > [id] => 3 > > [username] => normaluser > > [name] => miguel > > [email] => [email protected] > > [group_id] => 2 > > [active] => 1 > > [created] => 0000-00-00 00:00:00 > > [modified] => 0000-00-00 00:00:00 > > ) > > > ) > > [/code] > > ) > > > -- > > View this message in > > context:http://www.nabble.com/AuthComponent---Need-more-explanation-about-%22... > > Sent from the CakePHP mailing list archive at Nabble.com. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
