Received: by 10.236.154.170 with SMTP id h30mr12655787yhk.8.1338214148883; Mon, 28 May 2012 07:09:08 -0700 (PDT) X-BeenThere: turbogears@googlegroups.com Received: by 10.236.173.229 with SMTP id v65ls4486718yhl.0.gmail; Mon, 28 May 2012 07:09:04 -0700 (PDT) Received: by 10.236.154.170 with SMTP id h30mr12655612yhk.8.1338214144732; Mon, 28 May 2012 07:09:04 -0700 (PDT) Received: by 10.236.154.170 with SMTP id h30mr12655611yhk.8.1338214144720; Mon, 28 May 2012 07:09:04 -0700 (PDT) Return-Path: Received: from mail-yx0-f173.google.com (mail-yx0-f173.google.com [209.85.213.173]) by gmr-mx.google.com with ESMTPS id a57si9680382yhh.5.2012.05.28.07.09.04 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 May 2012 07:09:04 -0700 (PDT) Received-SPF: pass (google.com: domain of alessandro.mol...@gmail.com designates 209.85.213.173 as permitted sender) client-ip=209.85.213.173; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of alessandro.mol...@gmail.com designates 209.85.213.173 as permitted sender) smtp.mail=alessandro.mol...@gmail.com; dkim=pass header...@gmail.com Received: by mail-yx0-f173.google.com with SMTP id m4so1688124yen.32 for ; Mon, 28 May 2012 07:09:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jPsxPto/OS/kFNgB6hfJZ7mmG9M+/pP98FqUakxkNTc=; b=dz9BzNR6WajYYlCKve9kkie8VQJog5Wsgcrz/WV0IZJKLX2xvOLabEihu2pR/h/Y4K FH7rmpHy4CE0Muavf8hXzg5QOcD3yOqOfNJ5KNu8BHWvZnqBpcLPLlLv7DR0hKLOic8t QIHpq0AHlWzL26/Dg6YZqMr6QyVQHdFp8nuNzmT1uL1tCfyWEvPl+/TUS69d3jV7qHfy Hf7jppBqCOU2lFefntvhFmuqyou5VX6tTcT2Ip6YQj3blvOmm1yU6fujQNxp4YPh8nrG i/MrJ0I41WK6QtakFYo7dg98dnEWzmK/3OqXfuK9BbUdJrO+svA1wVQA8P1kaTpSklyZ r5QQ== MIME-Version: 1.0 Received: by 10.236.76.233 with SMTP id b69mr7939778yhe.52.1338214144647; Mon, 28 May 2012 07:09:04 -0700 (PDT) Received: by 10.100.134.6 with HTTP; Mon, 28 May 2012 07:09:04 -0700 (PDT) In-Reply-To: <408497ed-5432-4a65-8483-4e3e8306d...@t20g2000yqn.googlegroups.com> References: <408497ed-5432-4a65-8483-4e3e8306d...@t20g2000yqn.googlegroups.com> Date: Mon, 28 May 2012 16:09:04 +0200 Message-ID: Subject: Re: [TurboGears] Authenticated session expiration in TG 2.1 From: Alessandro Molina To: turbogears@googlegroups.com Content-Type: text/plain; charset=ISO-8859-1 Most simple way is to take a look at the login.html page. The remember me field sets the expiration of the authentication session, set it to an hidden input of any value you want it to last On Mon, May 28, 2012 at 10:23 AM, puska wrote: > Hi everyone, > > I am in the process of porting a TG 1.0 application to TG 2.1. One of > the things that looks like is not there anymore is expiring > authenticated sessions. In TG 1.0 there were visit and visit_identity > tables (I assume they had to do with session expiration). paster setup- > app does not create those tables anymore and my authenticated sessions > do not expire until I log out or close browser session. > I there a provision in TG 2.1 to expire authenticated sessions. Any > help or a pointer would be most appreciated. > > -- > You received this message because you are subscribed to the Google Groups "TurboGears" group. > To post to this group, send email to turbogears@googlegroups.com. > To unsubscribe from this group, send email to turbogears+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/turbogears?hl=en. >