Harish, In your User controller login action are you simply calling:
$this->Auth->login(); Or are you doing something else? And another question: why are you going to the login page with user login data already available? I don't think a logged in user has any legitimate business on the login page. There are lots of ways to handle things depending on how and why this is happening. - You could redirect logged in users who try to access the login page - You could not allow mid or low level users see high level page links and you could set special redirects to handle 'not high enough permission' vs 'not logged in' arrivals. - You could simply log out users when they arrive on the log in page (a bit harsh though) Regards, Don Regards, Don On May 12, 11:31 pm, Harish <[email protected]> wrote: > Yes. Thank you. I did a few things that solved it. First, changed to > 'routes' to point to 'users->login'. I had forgotten to do this. And > then included the $this->Auth->allow('*') in the users_controller's > beforeFilter. This solved the problem of cake throwing a 'You are not > authorized to view this' error message. However the userid and > password fields in the login form remain populated. Userid being > populated is not a problem, however password field should not have a > value! I have included array('value'=>'') in the password field in the > view. Can't figure out what else to do. > > Thank you very much. > Regards, > Harish > > On May 12, 9:42 pm, dreamingmind <[email protected]> wrote: > > > > > > > > > Harish, > > > My course would be to intervene in the process (with debug(); die;) > > and compare your assumptions to reality. > > > For example, you say: > > > > I have included $this->Auth->allow('display') in the controller > > > beforeFilter() function(for the relevant redirected page(s)). > > > but since you're bouncing, I have to wonder; are you really 'starting' > > on display? I wouldn't look for exotic solutions until you've verified > > that you've actually 'allow'ed the right locations. > > > For example, if you change to $this->Auth->allow('*') does it let you > > get in without problems? > > > I'd start putting debug() statements in here and there to evaluate > > exactly what is happening. > > > Hope this advice isn't too basic, but this sounds like you're > > assumptions are preventing you from 'seeing'. > > > Regards, > > Don > > > On May 11, 8:22 pm, Harish Amur <[email protected]> wrote: > > > > I know this issue has been discussed quite a bit early on. I did read many > > > posts, however I am not finding a solution, so I am going to ask again. > > > > I use Auth to authenticate. It is a simple user, password screen. However > > > whenever I start, I am taken to the login page with the error message 'You > > > are not authorized to access that location' already displayed and the > > > user/pass fields populated. If I click on login it works and I am > > > redirected > > > to the right page. > > > > I have included $this->Auth->allow('display') in the controller > > > beforeFilter() function(for the relevant redirected page(s)). I have also > > > included 'value'=>'' in the login.ctp. > > > > Is this to do with Cache? Some settings in the core.php? > > > > Regards, > > > Harish -- 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 [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
