Re: [OAUTH-WG] Error code for access token request
Eran Hammer <eran@hueniverse.com> Thu, 19 January 2012 22:59 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 685EA21F85DF for <oauth@ietfa.amsl.com>; Thu, 19 Jan 2012 14:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level:
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[AWL=-1.159, BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 iJT8EHLtLs7m for <oauth@ietfa.amsl.com>; Thu, 19 Jan 2012 14:59:45 -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 925B321F85D0 for <oauth@ietf.org>; Thu, 19 Jan 2012 14:59:45 -0800 (PST)
Received: (qmail 26321 invoked from network); 19 Jan 2012 22:59:42 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.46) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 19 Jan 2012 22:59:41 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Thu, 19 Jan 2012 15:59:20 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Antonio Sanso <asanso@adobe.com>
Date: Thu, 19 Jan 2012 15:59:11 -0700
Thread-Topic: Error code for access token request
Thread-Index: AczWzJk/mzsZWxKHS+ierrXjVwqRaAAMUo5w
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AAB963B1@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4A1DD0C1-77F2-4824-973A-25F225D94F93@adobe.com> <90C41DD21FB7C64BB94121FBBC2E723453A72D0CF5@P3PW5EX1MB01.EX1.SECURESERVER.NET> <966C829C-AD86-428C-984A-C5A806ECB399@adobe.com>
In-Reply-To: <966C829C-AD86-428C-984A-C5A806ECB399@adobe.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_90C41DD21FB7C64BB94121FBBC2E723453AAB963B1P3PW5EX1MB01E_"
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Error code for access token request
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, 19 Jan 2012 22:59:46 -0000
In the case of section 5, because this is a direct interaction with the client, the server should issue a 5xx response instead.
EHL
From: Antonio Sanso [mailto:asanso@adobe.com]
Sent: Thursday, January 19, 2012 9:06 AM
To: Eran Hammer
Cc: OAuth WG
Subject: Re: Error code for access token request
Hi Eran,
thanks a lot for your response.
As long as I understood from [1] though the error parameter is mandatory
error
REQUIRED. A single error code from the following:
Which one is appropriate in case of server error? I cannot see any that would suite...
Thanks in advance
Antonio
[1] http://tools.ietf.org/html/draft-ietf-oauth-v2-22#section-5.2
On Jan 9, 2012, at 5:11 PM, Eran Hammer wrote:
Just return HTTP 5xx. We needed the special error code because of the redirection flow.
EHL
From: oauth-bounces@ietf.org<mailto:oauth-bounces@ietf.org> [mailto:oauth-bounces@ietf.org]<mailto:[mailto:oauth-bounces@ietf.org]> On Behalf Of Antonio Sanso
Sent: Friday, December 30, 2011 10:22 AM
To: OAuth WG
Subject: [OAUTH-WG] Error code for access token request
Hi *,
Error response for Authorization Request defines some kind of server error code response:
server_error
The authorization server encountered an unexpected
condition which prevented it from fulfilling the request.
as in [0].
I was wondering if would be possible/useful having same for error code for access token request [1]
WDYT?
Regards
Antonio
[0] http://tools.ietf.org/html/draft-ietf-oauth-v2-22#section-4.1.2.1
[1] http://tools.ietf.org/html/draft-ietf-oauth-v2-22#section-5.2
- Re: [OAUTH-WG] Error code for access token request Eran Hammer
- [OAUTH-WG] Error code for access token request Antonio Sanso
- Re: [OAUTH-WG] Error code for access token request Antonio Sanso
- Re: [OAUTH-WG] Error code for access token request Eran Hammer