Your verbiage describes clearly what structure you need to create.
I have a very similar structure with a few of my sites, because I
support more than one authentication via  www.rpxnow.com which is a
service to support OpenID so my users can associate their account with
multiple login services (Google, Yahoo, Facebook) this enables them to
use an already existing UserName and Password which they don't have to
share with anyone. My site uses these other sites to authenticate I
get a token back which confirms the association and I grant them
access.

Your request really has nothing to do with Authentication. The
authentication role is still the same weather its the Primary User or
a Secondary User.
You should create a structure like this:
Accounts have many Users
Users has a Profile
Users belong to Accounts
Users have and belong to Groups (or Users belong to Groups) I like to
set this one up as a many to many relation.
Accounts have and belong to Groups

Mine is simular, however I have Company instead of Accounts as in
Companies have many Users
Users has a Profile
Users belong to Companies
Users have and belong to Groups
Companies have and belong to Groups

Then using the auth component each user can be authenticated as
normal.
Using ACL, ACOand ARO you can assign rules for specific members or
spacific Groups to be super users for that specific company with
rights to manage the users for that Company.
Also each Account or Company could then be assigned its own set of
access rules.

So really I do believe you get what your looking for out of the box,
once you get your models setup correctly and make use of both the Auth
components and the ACL components you should be well on your way.

On Jul 18, 7:31 pm, thatsgreat2345 <[email protected]> wrote:
> Yeah this isn't exactly a normal request, but you could somehow set up
> a that a User has a field inside itself that is user_id. So when their
> is a primary account it sets the field to 0, however when their is a
> secondary account it sets user_id to a parent account. So when Auth
> component tries to login it will only have to look in the users table,
> however you'll have to do some programming to sort out if there is a
> parent account or this is a secondary account.
>
> On Jul 18, 1:50 pm, mindpike <[email protected]> wrote:
>
> > Is the built in auth mechanisms in CakePHP able to handle a single
> > account that has multiple logins? I.E. Login Primary logs in on his
> > dashboard clicks add user adds user Secondary. User secondary logs in
> > with his user name and password but it is simply an alternative login
> > for the Primary sharing the same account?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to