another database table to existing CakePHP Auth/ACL. That's uncharted
territory for me. One idea:
1. Add your external database table to your CakePHP site as a Model
(ExternalUsers).
2. Keep your existing, authenticated users as another Model
(InternalUsers).
3. Combine both Models in a third Model (Users) including a
'grouping' field (User.group_id) to differentiate which Model they
each come from.
4. Set model Users as AROs in CakePHP Acl.
5. Give Users access to ACOs based (in part) upon the value of
User.group_id
Rob
On May 22, 5:12 pm, emmexx <emmeics...@gmail.com> wrote:
> On 22 Mag, 22:15, RobMaurer<robmau...@gmail.com> wrote:
>
> > If I understand your needs as written, it would seem simpler to stay
> > with CakePHP Auth/ACL and create a second tier of permissions for a
> > subset of Users who are also in the Users table. That would handle
> > authentication for you (the way you're already doing) and you would
> > grant those Users access to the create/update/delete views on your
> > models as needed.
>
> The problem is that the second group of users has its own table in
> another database.
> Those users are managed by another (non-cakephp) program and I'd
> rather prefer not to mess with it.
> Furthermore I would like not to manage permissions for those users.
> They simply need to enter some data in a field, data not that
> important.
> And the more the 2 systems are separated, the better.
>
> Anyway I'll think about your suggestion.
>
> Thank you
>
> maxx
--
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