Hi Bakers,

I am having a problem with ACL and Auth component. First the context :

1) I have several applications, and I am using a User / Group etc ..
plugin in order to the "public" site to process the login and the
redirect the user to ont of the application. The User / Group / Role
and some other table are stored in a separate database. This plugin
expect a dadabse configuration 'access' and that should be set in the
database.php of the application using the plugin. The $useDbConfig is
set 'access' into the plugin appModel.

2)In each application I have a database that contains all my
application tables as well as the the acl tables (acos / sros /
acos_aros). For the application this is the "default" configuration of
my dabase php. Each application has got a second configuration $access
that points to the  1) db.

I the application I use the Auth component in type "action". Here
start the problem when I want to check a controller/action using the
Auth. Indeed, being in one of my application I receive a message "no
tables users found for model User".

I have been into the code, and actually that comes from the db_acl
node method that does a ClassRegistry::init. Actually this the
ClassRegistry::init that output the error, because I guess, the plugin
name id not know. Indeed the model extracted from the User record is
User and not  plugin.User...

I have tried to set the userModel in the auth using "plugin.User", but
that can't work and would need lot's of modifications.

Well, I am asking if someone has got a solution for this, or maybe
there is an existing way in ACL to handle  Model.foreign key that are
in plugins ?

Thanks

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to