Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)
Eran Hammer <eran@hueniverse.com> Wed, 07 March 2012 23:58 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 E556411E8094 for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 15:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599]
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 4impVra6cLRF for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 15:58:17 -0800 (PST)
Received: from p3plex2out02.prod.phx3.secureserver.net (p3plex2out02.prod.phx3.secureserver.net [184.168.131.14]) by ietfa.amsl.com (Postfix) with ESMTP id CA65211E808C for <oauth@ietf.org>; Wed, 7 Mar 2012 15:58:16 -0800 (PST)
Received: from P3PW5EX1HT005.EX1.SECURESERVER.NET ([72.167.180.47]) by p3plex2out02.prod.phx3.secureserver.net with bizsmtp id inu91i00j11lQaG01nvoY2; Wed, 07 Mar 2012 16:55:48 -0700
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT005.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Wed, 7 Mar 2012 16:55:32 -0700
From: Eran Hammer <eran@hueniverse.com>
To: Roger Crew <crew@cs.stanford.edu>
Date: Wed, 07 Mar 2012 16:55:23 -0700
Thread-Topic: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)
Thread-Index: Aczl2ilWT6nLyLlSQtCoYNfpPEt95wW42oKQ
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AFCD4078@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <20160.24172.942808.563672@hagen.valhalla> <90C41DD21FB7C64BB94121FBBC2E723453AAB964C0@P3PW5EX1MB01.EX1.SECURESERVER.NET> <20273.36647.811224.493136@hagen.valhalla>
In-Reply-To: <20273.36647.811224.493136@hagen.valhalla>
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
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension response types (8.4)
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, 07 Mar 2012 23:58:18 -0000
Added: unsupported parameter value (other than grant type) EH > -----Original Message----- > From: Roger Crew [mailto:crew@cs.stanford.edu] > Sent: Tuesday, February 07, 2012 12:53 PM > To: Eran Hammer > Cc: oauth@ietf.org > Subject: RE: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and extension > response types (8.4) > > > > (2) [in 4.2.2.1] If the response_type is provided but unknown, > > > is that an 'invalid_request' (since this is clearly an > > > "unsupported parameter value") or is it an > > > 'unsupported_response_type'? > > > > > > Seems to me it should be the latter. If so, then... > > > ... > > > should the description for 'invalid_request' even be referring to > > > "unsupported" values at all? > > > ... > > > Section 5.2 has the same problem w.r.t. 'unsupported_grant_type' > > > > Changed the definition of invalid_request to: > > > > The request is missing a required parameter, includes an invalid > > parameter value, or is otherwise malformed. > > Just noticed in draft 23 that you changed 4.2.2.1 but didn't change 5.2, which > still refers to "unsupported" parameter values and thus similarly conflicts > with the definition of 'unsupported_grant_type'. > > > -- > Roger Crew > crew@cs.stanford.edu
- [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1 and… Roger Crew
- Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1… Roger Crew
- Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1… Eran Hammer
- Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1… Roger Crew
- Re: [OAUTH-WG] error codes in 4.1.2.1 and 4.2.2.1… Eran Hammer