So I've been working hard at understanding CakePHP and the Auth and ACL components. I'm not considering how a large scale implementation would. I'm building several simple applications requiring Auth and ACL.
Since they are all related I wanted to centralize a user's login so they don't have to register on each app. It was easy enough to do with just the Auth component. I just set the $useDbConfig variable for the User model and was good to go. I even managed to to get it working with the ACL component by setting the Acl.database setting in core/ config.php. But then I got to thinking, does centralizing the ACL lead to any issues. For example, every application will have a Comment model and while the group 'users' can comment on App1 they should not be able to comment on App2. I'm testing to see if this will work, but I just don't understand the ACL component well enough to be certain. The question comes down to - can the ACL component differentiate controllers of the same name? My initial thought is yes, because each controller will have a unique ACO id, and their subsequent actions will have unique ACO ids. So if I properly manage the aco table, all should be good. Any addtional input would be appreciated. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
