IETF Logo Mail Archive

[OAUTH-WG] Possibly incorrect IANA registry contents for Error Registry

"Emelia S." <emelia@brandedcode.com> Sun, 20 September 2026 16:36 UTC

Received: from smtp-1909.mail.infomaniak.ch (smtp-1909.mail.infomaniak.ch [IPv6:2001:1600:19:8e30::1909]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 06E3030 for <oauth@ietf.org>; Sun, 20 Sep 2026 16:36:56 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=brandedcode.com header.s=20250226 header.b=HGdoeoDo; dmarc=pass (policy=reject) header.from=brandedcode.com; spf=pass (mx.ietf.org: domain of emelia@brandedcode.com designates 2001:1600:19:8e30::1909 as permitted sender) smtp.mailfrom=emelia@brandedcode.com
Received: from smtp-4-0000.mail.infomaniak.ch (smtp-4-0000.mail.infomaniak.ch [10.7.10.107]) by smtp-4-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4hnsSw6H5jzcxR; Sun, 20 Sep 2026 18:36:48 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandedcode.com; s=20250226; t=1789922208; bh=VgvOKGjISfWv91AHxu7MZwV0RWmno9k+mKXccNZyDSk=; h=From:Date:Subject:To:From; b=HGdoeoDoz2AU/oPYI5m2psPSY2riD5Uyd/C7aFpdOj6Gl/UvgzeP2FmXeWocdkLiI krxYY6ws4C/4etIysI410Aa4bNkADjdgMryE3AdZ+TzwfYqIsPUlpockEuMtk5ydfH NhCKjqSlT6thMyEsSjmEUZtlu/tMtpuwnDJ+xUeWKVZxNLFWn7mad0i+pv7f+KLbeW JlE5rjM9W5R+2mmhJztUWv//k+y+86mUIXhynBLSTnctPSbKHQoJP5EOpkhs1X+bmo quhBNvCp517VD6ejpxp7hw6X3Aj4P0hfb5hcBYsTChfdDODWWN0cGzdlrtOVqAfFA7 iHqvkoVbMkRLw==
Received: from unknown by smtp-4-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4hnsSw2Pd3z1jS; Sun, 20 Sep 2026 18:36:48 +0200 (CEST)
From: "Emelia S." <emelia@brandedcode.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
Date: Sun, 20 Sep 2026 18:36:36 +0200
Message-Id: <9703C501-9D43-41FA-B4C4-C0055BED9A9B@brandedcode.com>
To: "oauth@ietf.org" <oauth@ietf.org>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
X-Infomaniak-Routing: alpha
X-Spamd-Bar: /
Message-ID-Hash: UL4L6BWWJOC7DFU7PF7IUC2X7YWUYE5L
X-Message-ID-Hash: UL4L6BWWJOC7DFU7PF7IUC2X7YWUYE5L
X-MailFrom: emelia@brandedcode.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-oauth.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [OAUTH-WG] Possibly incorrect IANA registry contents for Error Registry
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/GlT6Ue2LIOqi_JSdyL-6zKT8F2w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

Hi all,

In the OAuth Extensions Error Registry managed by IANA, invalid_client is listed as having a usage location of "token endpoint, authorization endpoint", citing RFC6749, however, RFC6749's Section 4.1.2.1 "Authorization Code Grant -> Authorization Response -> Error Response" does not list invalid_client.

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

I'm not sure where the IANA registry contents is from, given that RFC6749 does not include the initial registry contents. The only place invalid_client is listed in RFC6749 is on the token endpoint.

Can someone clarify if `invalid_client` is valid for the authorization endpoint and if that error is redirectable?

— Emelia

v2.46.0 | Report a Bug | By Email | System Status