On 24 Mag, 14:51, Rob Maurer wrote:
> Then it would seem the problem is adding authentication for users from
> another database table to existing CakePHP Auth/ACL. That's uncharted
> territory for me. One idea:
That is unchartered territory for me too.
The problem is that the solution you sugge
Then it would seem the problem is adding authentication for users from
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
On 22 Mag, 22:15, Rob Maurer 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 d
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
In one cake app I use Auth and Acl to authenticate users, as per
manual.
Now I need to let some users, not listed in users table but in another
database, edit the records of a table. Let's say for clarification
that they should manage their own profile.
What I want to do is:
1. let those users "a
