Re: [OAUTH-WG] Validation of a refresh token
Eran Hammer-Lahav <eran@hueniverse.com> Wed, 13 July 2011 22:25 UTC
Return-Path: <eran@hueniverse.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 B070F11E8084 for <oauth@ietfa.amsl.com>; Wed, 13 Jul 2011 15:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599]
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 Cf+E7k93dPAd for <oauth@ietfa.amsl.com>; Wed, 13 Jul 2011 15:25:55 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id AD2E111E8075 for <oauth@ietf.org>; Wed, 13 Jul 2011 15:25:55 -0700 (PDT)
Received: (qmail 24740 invoked from network); 13 Jul 2011 22:25:55 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 13 Jul 2011 22:25:55 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Wed, 13 Jul 2011 15:25:31 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "Zeltsan, Zachary (Zachary)" <zachary.zeltsan@alcatel-lucent.com>, 'OAuth WG' <oauth@ietf.org>
Date: Wed, 13 Jul 2011 15:25:18 -0700
Thread-Topic: Validation of a refresh token
Thread-Index: AcxBqvqzkcx538PDQPiVCHRdrdRHhwAAF/Ew
Message-ID: <90C41DD21FB7C64BB94121FBBC2E7234501D4A0932@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <5710F82C0E73B04FA559560098BF95B125087447E8@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <5710F82C0E73B04FA559560098BF95B125087447E8@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Validation of a refresh token
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: Wed, 13 Jul 2011 22:25:59 -0000
I think we can remove that line. The refresh token represents the original authorization and the server an decide when it is still valid. EHL > -----Original Message----- > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > Of Zeltsan, Zachary (Zachary) > Sent: Wednesday, July 13, 2011 3:20 PM > To: 'OAuth WG' > Subject: [OAUTH-WG] Validation of a refresh token > > > There is a requirement in the core specification (Section "6 Refreshing an > Access Token) that authorization server "MUST verify that the resource > owner's authorization is still valid" when issuing an access token in exchange > for a refresh token. How is such verification done (given that authorization > server does not interact with the resource owner at this stage)? What exactly > must be checked (e.g., a revocation list, expiration time, ...)? > > Zachary > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Validation of a refresh token Zeltsan, Zachary (Zachary)
- Re: [OAUTH-WG] Validation of a refresh token Eran Hammer-Lahav