Re: [OAUTH-WG] Error code for access token request

Eran Hammer <eran@hueniverse.com> Mon, 09 January 2012 16:11 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 D424521F8715 for <oauth@ietfa.amsl.com>; Mon, 9 Jan 2012 08:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level:
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.025, 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 hnHNcHS10ktr for <oauth@ietfa.amsl.com>; Mon, 9 Jan 2012 08:11:47 -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 D505321F86CC for <oauth@ietf.org>; Mon, 9 Jan 2012 08:11:46 -0800 (PST)
Received: (qmail 29807 invoked from network); 9 Jan 2012 16:11:45 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.46) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 9 Jan 2012 16:11:42 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Mon, 9 Jan 2012 09:11:31 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Antonio Sanso <asanso@adobe.com>, OAuth WG <oauth@ietf.org>
Date: Mon, 9 Jan 2012 09:11:15 -0700
Thread-Topic: Error code for access token request
Thread-Index: AczHH/oz+E6plhXyQYi/VbPh53dC0wHyTzcg
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453A72D0CF5@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4A1DD0C1-77F2-4824-973A-25F225D94F93@adobe.com>
In-Reply-To: <4A1DD0C1-77F2-4824-973A-25F225D94F93@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_90C41DD21FB7C64BB94121FBBC2E723453A72D0CF5P3PW5EX1MB01E_"
MIME-Version: 1.0
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: Mon, 09 Jan 2012 16:11:52 -0000

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] 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