Understand now, thank you very much, you've been extremely helpful!
I figured out sessions too by the way :)
Also, the login controller is still called when the user attempts to
authenticate, it just redirects it to in this case /verify_login if the
authentication is successful, otherwise it reports the authentication error
message to the login.kid template?
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Patrick Lewis
Sent: Saturday, January 06, 2007 5:18 AM
To: TurboGears
Subject: [TurboGears] Re: identity and login
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.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.6/617 - Release Date: 1/5/2007
11:11 AM
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.6/617 - Release Date: 1/5/2007
11:11 AM
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
