That's essentially what I'm doing on two web apps. I've got 3 levels
(guest,user,admin) and it seems to work fine for me.
Zoltan
www.nachogrid.ca - Toronto Nachos
On Mar 27, 9:47 pm, Grzesiek <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I`m building simple web app with users, profiles and so on.
>
>
Browse the acl/auth stuff here as a starting point, look at acl
behavior as well:
http://groups.google.com/group/cake-php/web/frequent-discussions
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To
On Thu, Mar 27, 2008 at 9:42 PM, Grzesiek <[EMAIL PROTECTED]> wrote:
> My question is: is this correct approach? Maybe I should authorize
> against model? If yes - how would you do it ?
Nothing wrong with your code -- you're correctly saying "if the
authorized user's id matches the id we want t
Hello,
I`m building simple web app with users, profiles and so on.
I`m using Auth Component for user authentication.
I ran into a problem - how to prevent logged user from i.e. editing
another user profile?
It turns out that Auth Component is capable of simple authorization
without the need fo
Hello,
I`m building simple web app with users, profiles and so on.
I`m using Auth Component for user authentication.
I ran into a problem - how to prevent logged user from i.e. editing
another user profile?
It turns out that Auth Component is capable of simple authorization
without the need fo