On Feb 13, 1:14 am, "Todd Martin" <[EMAIL PROTECTED]> wrote: > Thanks for the replies. I will read through the posted links. For my > case I'm not too concerned about security (like a bank), but I don't > want to be careless either. I don't need to be any more secure than > websites like Yahoo and Google that allow persistent logins.
I guess it should be possible to look reverse lookup the Visit for the login you wish to extend and change the expiry time to be some point in the future. You'd probably also need to change the "tg-visit" cookie's expiry to match too. That'd have to done some point _after_ the user has logged in though, so you've got a user id/object to work with. In the auto-generated login function you could probably do that just before "raise redirect(forward_url)" at the top of the login controller function. Haven't tried any of this myself, but I want to (at some point) enable longer duration logins without needing to extend the expiration on visits. John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
