[OAUTH-WG] Re: draft-chen-oauth-agent-authz-use-cases: data on responding to resource server challenges

Meiling Chen <chenmeiling@chinamobile.com> Fri, 09 October 2026 08:47 UTC

Received: from cmccmta6.chinamobile.com (cmccmta6.chinamobile.com [111.22.67.139]) by mx.ietf.org (Postfix) with ESMTP id 4A5C946; Fri, 09 Oct 2026 08:47:04 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=fail ("body hash did not verify") header.d=chinamobile.com header.s=default header.b=MDom6hSB; dmarc=pass (policy=none) header.from=chinamobile.com; spf=pass (mx.ietf.org: domain of chenmeiling@chinamobile.com designates 111.22.67.139 as permitted sender) smtp.mailfrom=chenmeiling@chinamobile.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chinamobile.com; s=default; l=0; h=from:subject:message-id:to:cc:mime-version; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=MDom6hSB8tCzQmJg/NLUVmEbYNG3yPq87qlf9+lz70xSBs75E0zhYvYdlF1qDjet6Rxcq2wP6Cei7 Hakm3hETJZcpMdtZmENMlBOLSA1h93vyVBQ2o1RgZfbVq27QePWu5EZLq1jSmbxnsMIgCSVq987+TV watXGpjlI5YnPRHw=
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from mail.dlp.master (unknown[10.188.0.87]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee16ac8aa0625e-99b42; Fri, 09 Oct 2026 16:47:02 +0800 (CST)
X-RM-TRANSID: 2ee16ac8aa0625e-99b42
Received: from wxh.mailtest (localhost [127.0.0.1]) by mail.dlp.master (Postfix) with ESMTP id 2773615A02F5; Fri, 9 Oct 2026 16:47:02 +0800 (CST)
Received: from spf.mail.chinamobile.com (unknown [10.230.70.214]) by mail.dlp.master (Postfix) with ESMTP id 86E4E15A02F5; Fri, 9 Oct 2026 16:46:41 +0800 (CST)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from DESKTOP-U9UKLCC (unknown[10.2.49.210]) by rmsmtp-syy-appsvr07-12007 (RichMail) with SMTP id 2ee76ac8a9ef7b7-3988d; Fri, 09 Oct 2026 16:46:41 +0800 (CST)
X-RM-TRANSID: 2ee76ac8a9ef7b7-3988d
Date: Fri, 09 Oct 2026 16:46:40 +0800
From: Meiling Chen <chenmeiling@chinamobile.com>
To: Sharma <laxsharma79@gmail.com>, oauth <oauth@ietf.org>
References: <CAOX9xW7A5XqLCvqBeF9MFyX-XRngo=gVUmMC55NpjCCeVyawKg@mail.gmail.com>
X-Priority: 3
X-GUID: 1E12B454-B5EB-435D-90E2-87832C850C55
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.542[cn]
Mime-Version: 1.0
Message-ID: <202610091646392006771@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart130661123162_=----"
X-Spamd-Bar: ---------------------
Message-ID-Hash: UFX7AJYRPMMXYVJQ7N6P4IJAXEDMVLUN
X-Message-ID-Hash: UFX7AJYRPMMXYVJQ7N6P4IJAXEDMVLUN
X-MailFrom: forwardingalgorithm@dmarc.ietf.org
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: draft-chen-oauth-agent-authz-use-cases <draft-chen-oauth-agent-authz-use-cases@ietf.org>
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [OAUTH-WG] Re: draft-chen-oauth-agent-authz-use-cases: data on responding to resource server challenges
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/IP-xhw-xxAApGblbY5LBqb9LfqM>
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 Laxmikant,
Just a quick follow-up to let you know that we have seen the proposed text you submitted on GitHub (Issue #30). 
Thank you for putting this together and opening the issue so quickly! We will review the text and incorporate it into the draft as soon as possible. 
We will keep you and the working group updated once the new version is ready.
Best regards,
Meiling


chenmeiling@chinamobile.com
 
From: Laxmikant Sharma
Date: 2026-09-25 12:58
To: oauth
CC: draft-chen-oauth-agent-authz-use-cases
Subject: draft-chen-oauth-agent-authz-use-cases: data on responding to resource server challenges
Hi all,

Ahead of the 19 October interim on agent authorization use cases
and gaps, here is some data on one of the gaps in
draft-chen-oauth-agent-authz-use-cases. Section 6 (item 2) notes
that the framework has no built-in mechanism for an agent "to
respond to a real-time authorization challenge from a resource
server".

In September I ran eight shipped AI agents that act as MCP
clients, in their mid-September releases, against a resource
server that answered the first request with 401 and a
WWW-Authenticate header carrying resource_metadata. The
authorization server offered the authorization code grant with
PKCE and accepted both client ID metadata documents and dynamic
registration. Each client ran in a terminal on a machine with a
browser, and a scripted test user completed any sign-in page a
client opened or printed.

In one-shot mode, one client completed the grant on its own, and a
second did so only after the user set a per-server flag in its
configuration. Two fetched the protected resource metadata, one of
them also registered a client, and both stopped there. The other
four made no authorization attempt, although one of them opened
the browser within seconds and completed the grant when run as an
interactive session instead. In a separate run the day before, all
eight completed the same grant through their own sign-in steps.

So every client can run the grant, and whether it runs it on a
challenge is left to the client. A client that won't act on the
challenge also has no standard way to say so, which leaves the
resource server nothing to fall back on.

Use Case 5 (Section 4.1.6) covers first connection when there is
no front channel. This is the complementary case, where the front
channel exists and the client doesn't use it. If the authors think
it belongs in the document, I'm glad to open an issue on their
tracker with proposed text. I also plan to publish the harness and
the records once each client's maintainers have seen their results.

Thanks,
Laxmikant Sharma