IETF Logo Mail Archive

Re: [OAUTH-WG] IANA registry for error codes of RFC6749 section 5.2?

Justin Richer <jricher@mit.edu> Thu, 10 October 2019 15:02 UTC

Return-Path: <jricher@mit.edu>
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 6AE32120119 for <oauth@ietfa.amsl.com>; Thu, 10 Oct 2019 08:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxeqGpiw922L for <oauth@ietfa.amsl.com>; Thu, 10 Oct 2019 08:02:56 -0700 (PDT)
Received: from outgoing-exchange-1.mit.edu (outgoing-exchange-1.mit.edu [18.9.28.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8CFE12001A for <oauth@ietf.org>; Thu, 10 Oct 2019 08:02:56 -0700 (PDT)
Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id x9AF2cQo015000; Thu, 10 Oct 2019 11:02:54 -0400
Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 10 Oct 2019 11:02:25 -0400
Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by oc11expo18.exchange.mit.edu (18.9.4.49) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 10 Oct 2019 11:02:29 -0400
Received: from oc11expo18.exchange.mit.edu ([18.9.4.49]) by oc11expo18.exchange.mit.edu ([18.9.4.49]) with mapi id 15.00.1365.000; Thu, 10 Oct 2019 11:02:29 -0400
From: Justin Richer <jricher@mit.edu>
To: Ludwig Seitz <ludwig.seitz@ri.se>
CC: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] IANA registry for error codes of RFC6749 section 5.2?
Thread-Index: AQHVf0tExLJXeLc6JU+rXDVO16K0Z6dUO+4A
Date: Thu, 10 Oct 2019 15:02:28 +0000
Message-ID: <FAAA32AB-8EAB-405E-9AEE-4E78A53018CD@mit.edu>
References: <08fd478d-233b-25e8-cb53-e2546596c329@ri.se>
In-Reply-To: <08fd478d-233b-25e8-cb53-e2546596c329@ri.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [71.174.62.56]
Content-Type: multipart/alternative; boundary="_000_FAAA32AB8EAB405E9AEE4E78A53018CDmitedu_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/iLkCxVcyBxkPQQLBRcaaEkHFcP4>
Subject: Re: [OAUTH-WG] IANA registry for error codes of RFC6749 section 5.2?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 10 Oct 2019 15:02:59 -0000

They are in that registry as the “token endpoint response” error codes. RFC8628 adds new ones.

I think that 6749 failed to put in the base ones.

— Justin

On Oct 10, 2019, at 5:15 AM, Ludwig Seitz <ludwig.seitz@ri.se<mailto:ludwig.seitz@ri.se>> wrote:

Hello OAuth WG,

while addressing some AD review comments on draft-ietf-ace-oauth-authz, I've come across a question I think you can help me with:

I was previously laboring under the misconception that the error codes defined in

https://tools.ietf.org/html/rfc6749#section-5.2

are registered here:

https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml#extensions-error

Which is apparently not the case. Is there another registry that one should use (e.g. if one needs to add new error codes)?

If there is none (which seems to be the case), should we create one?

Regards,

Ludwig

--
Ludwig Seitz, PhD
Security Lab, RISE
Phone +46(0)70-349 92 51

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

v2.23.0 | Report a Bug | By Email