I'm working on an authentication/authorization solution for my current project, so am trying to save myself a lot of work by using the dAuth component ( http://bakery.cakephp.org/articles/view/introduction-to-dauth-v0-3 ) and the PhpGACL for Cake plugin ( http://cakeforge.org/projects/phpgacl-cake/ )
First of all, thanks to the developers of these add-ons, I'm having good success so far. Basically, I wanted to customize the solution to meet the project's needs. It won't be needing any ARO's other than Users, and to keep things simple, I decided I wanted dAuth to use the same table for "users" that phpgacl does (e.g. "aro"). However, dAuth needs a password, email and username field and the User model wants a table called "users". I didn't want to have to modify the core code for these add-ons unless absolutely necessary. So, what I did was added two fields to the "aro" table for password and email. Then, I created a MySQL 5 view called "users" which views the "aro" table and uses the alias "username" for the "aro" table's "value" field. My theory is this: Since the "value" field is used as a unique identifier for ARO's by phpgacl, and dAuth wants to make sure "usernames" are unique, why not use the same field? Preliminary tests seem to show that everything works. I've seen older posts by Nate et al. talking about MySQL views not being officially supported. So, I thought maybe I'd run this scenario past the community to see if I'm setting myself up for some kind of trouble I'm not aware of. Many thanks in advance! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
