IETF Logo Mail Archive

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

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

Received: from smtp-8fad.mail.infomaniak.ch (smtp-8fad.mail.infomaniak.ch [83.166.143.173]) (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 E5D2931 for <oauth@ietf.org>; Sun, 20 Sep 2026 21:16:57 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=brandedcode.com header.s=20250226 header.b=IWpr9T0M; dmarc=pass (policy=reject) header.from=brandedcode.com; spf=pass (mx.ietf.org: domain of emelia@brandedcode.com designates 83.166.143.173 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 4hnzh269LLzpk8; Sun, 20 Sep 2026 23:16:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brandedcode.com; s=20250226; t=1789939010; bh=ORXW02qPWCCrBIR8CvVhpgVck3kz/TBSj8YPBqAOrY4=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=IWpr9T0MMuQRZZWB86dbMm0i73SYpC8LmL/7i8kljGkpAi4MZsD+5BxToJFqsxvWv umjlnI05FOTAiwoOfeZr4HtRQIfXXb8Hs7o0hq8NNZJYvqvS0zqsrPNlvhX+RoDXCa 2c8MG5grhnFxDhW4kLi7Lo1YMITRFBJSI3XDnED6yptkYXaTGb+bt5RpEQ+DpE3JZu 8Nae1PNZplVaRg9Gx5PPhZAIBT0TozXtM9xfkyXDvsBkCn/4iGwjUdu3SXxmdNGimO fcLeCZkRMzQmSBltd+PKD47f4y/kegI/6DPfIIYgYHYlAhnrcAe4Dp3p5WiddCAQh5 CyVjiayqDmasw==
Received: from unknown by smtp-4-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4hnzh21fy9z4kH; Sun, 20 Sep 2026 23:16:50 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_355812FD-351B-417D-A221-65FAAFE7FB6C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
From: "Emelia S." <emelia@brandedcode.com>
In-Reply-To: <CAJot-L0oMSeasYFZXHLxRnd6+jR+xHmTYFaFv4Pp4t=K37rjqw@mail.gmail.com>
Date: Sun, 20 Sep 2026 23:16:38 +0200
Message-Id: <10BABC07-85CF-4A91-BF6A-9F7C8D95224E@brandedcode.com>
References: <9703C501-9D43-41FA-B4C4-C0055BED9A9B@brandedcode.com> <CAJot-L0oMSeasYFZXHLxRnd6+jR+xHmTYFaFv4Pp4t=K37rjqw@mail.gmail.com>
To: Warren Parad <wparad=40rhosys.ch@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
X-Infomaniak-Routing: alpha
X-Spamd-Bar: /
Message-ID-Hash: TTCTD4MS3Y4NTWVTWOGP36AJPJGCRNOW
X-Message-ID-Hash: TTCTD4MS3Y4NTWVTWOGP36AJPJGCRNOW
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
CC: "Emelia S." <emelia=40brandedcode.com@dmarc.ietf.org>, oauth <oauth@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [OAUTH-WG] Re: Possibly incorrect IANA registry contents for Error Registry
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/v4AZ8DUt1kEQ9bzViHIbxF9KvRk>
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 Warren,

Can you cite a specification that makes invalid_client valid for usage with the authorization endpoint? I can't see any specification text for this.

Thanks,
Emelia

> On 20 Sep 2026, at 18:58, Warren Parad <wparad=40rhosys.ch@dmarc.ietf.org> wrote:
> 
> Yes it's valid. No it isn't redirectable.
> 
> On Sun, Sep 20, 2026, 18:37 Emelia S. <emelia=40brandedcode.com@dmarc.ietf.org <mailto:40brandedcode.com@dmarc.ietf.org>> wrote:
>> 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
>> _______________________________________________
>> OAuth mailing list -- oauth@ietf.org <mailto:oauth@ietf.org>
>> To unsubscribe send an email to oauth-leave@ietf.org <mailto:oauth-leave@ietf.org>
> _______________________________________________
> OAuth mailing list -- oauth@ietf.org
> To unsubscribe send an email to oauth-leave@ietf.org

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