[OAUTH-WG] Re: New draft: Presenting Issuer-Signed JWT Credentials to Resource Servers with DPoP

Su-hyeon Forten Lee <nine01223@naver.com> Sat, 10 October 2026 00:16 UTC

Received: from cvsmtppost02.nm.naver.com (cvsmtppost02.nm.naver.com [114.111.35.100]) (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 6353E46 for <oauth@ietf.org>; Sat, 10 Oct 2026 00:16:08 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=naver.com header.s=s20171208 header.b=drXa2Ekb; spf=pass (mx.ietf.org: domain of nine01223@naver.com designates 114.111.35.100 as permitted sender) smtp.mailfrom=nine01223@naver.com; dmarc=pass (policy=none) header.from=naver.com
X-Originating-IP: 118.36.136.231
X-Works-Smtp-Source: Ylb9FxulFqJCpNm/Fxv/WHF0
Received: from nv1s-hmac-real-0 ([10.180.31.91]) by cvsmtppost02.nm.naver.com with ESMTP id 04cMnievTFO6FPCL4BFdvw for <oauth@ietf.org>; Sat, 10 Oct 2026 00:15:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=naver.com; s=s20171208; t=1791591358; bh=3ibi+qKwrrTqkT9oO7LG8PfI90SmwRESdkiP6kdbrMo=; h=Message-ID:Date:From:To:Subject:From:Subject:Feedback-ID: X-Works-Security; b=drXa2Ekbk7qBwqkxtY7RojjML6WbkaX177XSvNw6Q3t92jHcjyphycX7/j2PktcdB 70tHEjDQMxCuKwnbJWQDCaRmV2kmTxC2jIucGZuKem8VhUWsFZHRIIvS9YdVTFIsvr LYOVlIpMawlR9JUnVJFuClSkwTcnCD/YBfLOVSxm9an99NClVyqwniDIeTsRenWgOz b+7OztMLKMhJuHBBOcQb4bSFvFsCluCWkiQaXnRtN1DNoXdq9uYK/oGQuNOo7PWhSZ Y6PZOTCPoiiHAuJrTXTJ7wdcI4ebfbsNanAr/dCEAFObxmGszANaMCnvsUZJpJC/C+ K0y44s3yNSOYw==
X-Session-ID: e453b8554bae413394f022a69b89d5b00a9cbedb0a76622dbbc497cb25f90ee9
MIME-Version: 1.0
Message-ID: <30881db37f8593b04387fd51e2e5cfaf@cweb012.nm>
Date: Sat, 10 Oct 2026 09:15:58 +0900
From: Su-hyeon Forten Lee <nine01223@naver.com>
In-Reply-To: <tencent_11695B223271F8A412CF356A@qq.com>
References: <tencent_11695B223271F8A412CF356A@qq.com>
Importance: normal
To: Jijie Wei <pki@varwof.com>
X-Originating-IP: 118.36.136.231
X-Works-Send-Opt: Sse0W405jHmmjAKZKoumjAiYKxg/KqbZFAtlFNwYKBmm
Content-Type: multipart/alternative; boundary="-----Boundary-WM=_7f0494df5700.1791591358872"
X-Spamd-Bar: -------------------
Message-ID-Hash: U4E3E6VONG4WNC7VNCDD63KLLFAKJHFO
X-Message-ID-Hash: U4E3E6VONG4WNC7VNCDD63KLLFAKJHFO
X-MailFrom: nine01223@naver.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: oauth@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [OAUTH-WG] Re: New draft: Presenting Issuer-Signed JWT Credentials to Resource Servers with DPoP
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/IEWQqWzfs0GkLShp8kzP61veFxU>
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>

Jijie,

Thank you for this. You have put the question more precisely than I did, and the Section 9 point is well taken.

Yes, that is the gap I meant, and I think reusing Section 9 is the answer.

On the nonce, the value belongs to the resource server that issues and checks it, not to DPoP. When the same resource server verifies both the DPoP proof and the KB-JWT, and both are signed with the key in cnf, a nonce it supplied under Section 9 is a nonce the verifier provided in RFC 9901's sense, whichever header carried it.

On aud, the natural value is the resource identifier the resource server already expects in the token's aud (the RFC 8707 / RFC 9728 identifier), so that the KB-JWT names the same party the token does.

Thanks again for taking the time to work through it.

Best,
Su-hyeon

-----Original Message-----
From: "Jijie Wei"<pki@varwof.com>
To: "oauth"<oauth@ietf.org>;
Cc: "nine01223"<nine01223@naver.com>;
Sent: 2026-10-07 (수) 23:29:46 (GMT+09:00)
Subject: [OAUTH-WG] Re: New draft: Presenting Issuer-Signed JWT Credentials to Resource Servers with DPoP

Su-hyeon,

On the nonce half. For an unsolicited call the delivery is defined, though not
in RFC 9901: RFC 9449 Section 9 has the resource server answer a request that
carries no nonce, using a 401 with the use_dpop_nonce error and a DPoP-Nonce
header, and the client retries with that value in the proof. So a resource
server can supply a nonce to a client that never asked it for one.

What that leaves open is aud. The proof binds htu and htm, not the audience of
the credential, and RFC 9901 leaves a KB-JWT's aud to the protocol in use.

So is the gap you mean the KB-JWT equivalent of Section 9 -- an HTTP-level
nonce and audience binding defined for a direct credential presentation -- and
would reusing Section 9 be the intended answer, or does that not carry,
because the challenge and the nonce belong to DPoP rather than to the
credential?

[Drafted with AI assistance; I have checked every point and agree with it.]

Best,
Jijie Wei
_______________________________________________
OAuth mailing list -- oauth@ietf.org
To unsubscribe send an email to oauth-leave@ietf.org