Return-Path: <leleuj@gmail.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 E2F0721F8498 for <oauth@ietfa.amsl.com>;
 Sun, 19 Aug 2012 01:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.000,
 BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3,
 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 EBO8e4U2pjCk for
 <oauth@ietfa.amsl.com>; Sun, 19 Aug 2012 01:25:30 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com
 [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 00F2C21F848F for
 <oauth@ietf.org>; Sun, 19 Aug 2012 01:25:29 -0700 (PDT)
Received: by lahm15 with SMTP id m15so2929225lah.31 for <oauth@ietf.org>;
 Sun, 19 Aug 2012 01:25:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=qYPoXScldJLjCbCOj2+3WPfD8X4OnsdqkO0nIEFEC68=;
 b=v83J6Qe9tthP1ZTZtlzWfGe1HYBvOReiF1HutAksGD4ISESk6MmuDz2NmGMsuRdzh0
 KZdep+dx3cU8TxHpyEARnmmKMTCayFI7ZI/ejv/KSNh2fTaRMcqL76KNKvbqv593O1kt
 oSY5VtadXKKla71Mxr/DC/3ZF5L0No8ma0MoxlZUwpVTWZ8TfUsczMnrz8JwACZ1SyTI
 +36mPoY0p9kSH+eWP3jDVZzi3unL5AGoCUUnRUj7QpoQF9X7Wq1ecfacTXVRuIYKNBfu
 wBX61RI8yr1WHiAtIzqJqzLh8I9FDQ9PybXDsP/G8Yyad2sWWS/Lw6ngNvGn0mG0lNI4 /yrw==
MIME-Version: 1.0
Received: by 10.152.146.169 with SMTP id td9mr10075092lab.42.1345364728833;
 Sun, 19 Aug 2012 01:25:28 -0700 (PDT)
Received: by 10.112.48.161 with HTTP; Sun, 19 Aug 2012 01:25:28 -0700 (PDT)
Date: Sun, 19 Aug 2012 10:25:28 +0200
Message-ID: <CAP279Lxk5+=2B3cFLzS=teRYu2qWbg9Ny263pfDpBRueC7pF+A@mail.gmail.com>
From: =?ISO-8859-1?B?Suly9G1lIExFTEVV?= <leleuj@gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary=e89a8f234589c1664a04c79a227e
Subject: [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 08:25:31 -0000

--e89a8f234589c1664a04c79a227e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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=E9r=F4me

--e89a8f234589c1664a04c79a227e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>I might be misunderstanding the OAuth 2.0 spec (part=
 5.1, &quot;expires_in&quot; property), but I understand that the timeout o=
f the access token is a hard one (amount of time between creation and expir=
ation).</div>
<div><br></div><div>Am I right ?</div><div><br></div><div>Can we have a mul=
tiple use timeout ? A sliding window timeout ? Or a combination of all ?</d=
iv><div><br></div><div>Thanks.</div><div>Best regards,</div><div>J=E9r=F4me=
</div>
<div><br></div>

--e89a8f234589c1664a04c79a227e--