Re: [OAUTH-WG] Access token timeout
John Bradley <ve7jtb@ve7jtb.com> Sun, 19 August 2012 17:41 UTC
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2280621F8596 for <oauth@ietfa.amsl.com>; Sun, 19 Aug 2012 10:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level:
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBSYBWFBmHPH for <oauth@ietfa.amsl.com>; Sun, 19 Aug 2012 10:41:12 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 685D321F852C for <oauth@ietf.org>; Sun, 19 Aug 2012 10:41:12 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so5261755ghb.31 for <oauth@ietf.org>; Sun, 19 Aug 2012 10:41:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=5+kZ4yzcUOR5t3NnWWYGDM8jtSit6LTuprLHwAhlzwo=; b=hK/gmvZ4kDWbVP2vGzItqoyfPCabFekgEugTYPXL1kPDhGJFIFf42qKBSXEcaNeL7Z /6ojJsFYtKuCxIrYPtlV1q44LsNjltEC/5Vxz5ObfnZR0FaWqPb1PTQU4exnKLDd+/54 RTJxqvMlN6ABsVUTMSvFCzjgc3CaFvVfvX9REsUxMEuiaL36SEALXgbm3WpdDY9QdDJE xZa/bMbQI/3C1+C/xjY3iX3UquMnjB/7yQRAwDuo1sPENbJV3G3oVftsBd64K/OQH2qm tesmbv7fFzUiHAsjcRj9Y2Jk/FP9Xlwpa2MNTZ27knEfJPkMwo+qwTnybMPSmj/q/bJc ku3A==
Received: by 10.236.136.39 with SMTP id v27mr17561173yhi.96.1345398071899; Sun, 19 Aug 2012 10:41:11 -0700 (PDT)
Received: from [192.168.1.39] (190-20-20-82.baf.movistar.cl. [190.20.20.82]) by mx.google.com with ESMTPS id t57sm25136551yhg.0.2012.08.19.10.41.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 19 Aug 2012 10:41:11 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DB8B400A-38B8-43DC-8FF7-FAE697AB6843"
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <1345397735.4226.YahooMailNeo@web31809.mail.mud.yahoo.com>
Date: Sun, 19 Aug 2012 13:40:59 -0400
Message-Id: <8E82B87D-B819-462A-8546-6E20CA3B48CA@ve7jtb.com>
References: <CAP279Lxk5+=2B3cFLzS=teRYu2qWbg9Ny263pfDpBRueC7pF+A@mail.gmail.com> <1345397735.4226.YahooMailNeo@web31809.mail.mud.yahoo.com>
To: William Mills <wmills_92105@yahoo.com>
X-Mailer: Apple Mail (2.1280)
X-Gm-Message-State: ALoCoQksRBhJkUMnCa5xM2Do7TRUu8uTAzG77yq3pTTRdumyQbTeJL+B7GGHD720u30NQctngo0X
Cc: "oauth@ietf.org" <oauth@ietf.org>, Jérôme LELEU <leleuj@gmail.com>
Subject: Re: [OAUTH-WG] Access token timeout
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Aug 2012 17:41:13 -0000
A token can always expire in less than that time. I have seen deployments that use sliding windows and single use access tokens. In those cases the "expires_in" is sent as a Max time before the token will expire. A client always needs to be prepared that a token will have been revoked or expired and fall back to using the refresh token, or reauthorize. John B. On 2012-08-19, at 1:35 PM, William Mills wrote: > It's a hint to the client of when the token will probably expire. There was a lot of discussion on what the right way to go was and there were several "camps" on the right strategy choice would be, but in the end a very simple solution was chosen. Most folks agreed that having more than one way to go was not worth the complexity, so this single one was picked. > > From: Jérôme LELEU <leleuj@gmail.com> > To: oauth@ietf.org > Sent: Sunday, August 19, 2012 1:25 AM > Subject: [OAUTH-WG] Access token timeout > > Hi, > > I might be misunderstanding the OAuth 2.0 spec (part 5.1, "expires_in" property), but I understand that the timeout of the access token is a hard one (amount of time between creation and expiration). > > Am I right ? > > Can we have a multiple use timeout ? A sliding window timeout ? Or a combination of all ? > > Thanks. > Best regards, > Jérôme > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Access token timeout Jérôme LELEU
- Re: [OAUTH-WG] Access token timeout William Mills
- Re: [OAUTH-WG] Access token timeout John Bradley
- Re: [OAUTH-WG] Access token timeout Guangqing Deng
- Re: [OAUTH-WG] Access token timeout Justin Richer
- Re: [OAUTH-WG] Access token timeout Justin Richer