IETF Logo Mail Archive

Re: [OAUTH-WG] error response for invalid refresh token

Eran Hammer <eran@hueniverse.com> Thu, 08 March 2012 00:41 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 6579111E8085 for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 16:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level:
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLCOS3DI+xEs for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 16:41:02 -0800 (PST)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id BA7D711E8080 for <oauth@ietf.org>; Wed, 7 Mar 2012 16:41:02 -0800 (PST)
Received: (qmail 4691 invoked from network); 8 Mar 2012 00:41:02 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.46) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 8 Mar 2012 00:41:02 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Wed, 7 Mar 2012 17:40:32 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Buhake Sindi <buhake@googlemail.com>
Date: Wed, 07 Mar 2012 17:40:24 -0700
Thread-Topic: [OAUTH-WG] error response for invalid refresh token
Thread-Index: AczwrRc850XNpSkXRK+RkIDjBTsUCwMFu2hw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AFCD407F@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <CAOqH_VV4uCjyz-UP9AhNoQPuesv6Z0Wbi7Zt=tz-B4qXh0efgw@mail.gmail.com> <CABUp4f6TdFcPXHPYS2B7kZK_=qZ3RESWswO=rDfo_tZvYUrjQg@mail.gmail.com>
In-Reply-To: <CABUp4f6TdFcPXHPYS2B7kZK_=qZ3RESWswO=rDfo_tZvYUrjQg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E723453AFCD407FP3PW5EX1MB01E_"
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] error response for invalid 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: Thu, 08 Mar 2012 00:41:03 -0000

Invalid_grand is correct.

EH

From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Buhake Sindi
Sent: Tuesday, February 21, 2012 7:16 AM
To: Peter Brindisi
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] error response for invalid refresh token

Hi
invalid_grant

The provided authorization grant (e.g. authorization code,
resource owner credentials) is invalid, expired, revoked, does
not match the redirection URI used

I would think that the refresh_token is an authorization code that needs refreshing, so this would be valid.


On 21 February 2012 15:33, Peter Brindisi <peter.brindisi@gmail.com<mailto:peter.brindisi@gmail.com>> wrote:
Hi all,

I am currently implementing version 23 of the oauth2 spec, and I came across a bit of ambiguity. What is the appropriate error code for an invalid refresh token? I am unsure whether it should be 'invalid_grant' or 'invalid_request'. Neither seems 100% clear.

Thanks in advance!

Best,
Peter

_______________________________________________
OAuth mailing list
OAuth@ietf.org<mailto:OAuth@ietf.org>
https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email