That works fine when you go straight to the /login page. But, if you go to a protected page like /secret (and aren't already authenticated), the progression goes something like this:
- user goes to /secret - internally, user is redirected to /login. Browser url still appears to say /secret - the target of the login form is /secret - once correct credentials are provided, the user can see what is at /secret So, the login controller is never called once the user is authenticated. It displays the form, but the request doesn't travel back through it. If you don't have any permission restricted controllers, then yes, you could just modify login. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
