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>
Message-ID-Hash: UL4L6BWWJOC7DFU7PF7IUC2X7YWUYE5L
Precedence: list
Subject: [OAUTH-WG] Possibly incorrect IANA registry contents for Error Registry
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/oauth/GlT6Ue2LIOqi_JSdyL-6zKT8F2w>

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?

=E2=80=94 Emelia=