[OAUTH-WG] 回复:draft-liu-oauth-authorization-evidence-02: an approver-side signature for 9.4

"刘大鹏(鹏成)" <max.ldp@alibaba-inc.com> Tue, 10 November 2026 16:21 UTC

Received: from out0-207.mail.aliyun.com (out0-207.mail.aliyun.com [140.205.0.207]) (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 C1BB447 for <oauth@ietf.org>; Tue, 10 Nov 2026 16:21:50 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=alibaba-inc.com header.s=default header.b=TqS+sjLD; spf=pass (mx.ietf.org: domain of max.ldp@alibaba-inc.com designates 140.205.0.207 as permitted sender) smtp.mailfrom=max.ldp@alibaba-inc.com; dmarc=pass (policy=quarantine) header.from=alibaba-inc.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1794327700; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=BByH1FCCxKBgSKmMknAP6ACyy6iCfBpeHczY/GItIuM=; b=TqS+sjLDEkd9lJDiRpPhBGrNF9of2xFC6+ASq/OL9FOc4M6QQvmiOlU7P0OyGrJSMGFDJ7pV2ceZkjmNHxTqVOIhgsrGATACnLFzDBURqlZpx7Y0HKi4EaJyO5EbKW3k2JU4+3QfxGCoxTTfH5O+3QPuDzn9KOSGyXOX4eRdfK0=
X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R141e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=maildocker-contentspam033040092104;MF=max.ldp@alibaba-inc.com;NM=1;PH=DW;RN=5;SR=0;TI=W4_0.2.3_v5ForWebDing_21192965_1794300812720_o7001c129g;
Received: from WS-web (max.ldp@alibaba-inc.com[W4_0.2.3_v5ForWebDing_21192965_1794300812720_o7001c129g] cluster:ay29) at Wed, 11 Nov 2026 00:21:33 +0800
Date: Wed, 11 Nov 2026 00:21:33 +0800
From: "刘大鹏(鹏成)" <max.ldp@alibaba-inc.com>
To: Mohamad Khalil Yossif <mohamad@yuthent.com>, oauth <oauth@ietf.org>
Message-ID: <a4eeb7c8-e309-4d7c-8849-f8056d8d528a.max.ldp@alibaba-inc.com>
X-Mailer: [Alimail-Mailagent][W4_0.2.3][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-im-through: {"version":"v1.0"}
References: <1A6A2BBF-6723-41AB-A0B9-1C56E3D7C9B1@yuthent.com> <1A6A2BBF-6723-41AB-A0B9-1C56E3D7C9B1@yuthent.com>
x-aliyun-mail-creator: W4_0.2.3_v5ForWebDing_QvNTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNykgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzE1Ni4wLjAuMCBTYWZhcmkvNTM3LjM2La
In-Reply-To: <1A6A2BBF-6723-41AB-A0B9-1C56E3D7C9B1@yuthent.com>
x-aliyun-mailtrack: {"foreign-track":"0"}
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_2406_7f93fdffe700_6af3448d_20a210"
X-Spamd-Bar: -----------------
Message-ID-Hash: GAZ2JISI3SRBFPSC6VB6D2N3365COJJJ
X-Message-ID-Hash: GAZ2JISI3SRBFPSC6VB6D2N3365COJJJ
X-MailFrom: max.ldp@alibaba-inc.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: "朱红儒(茱滴)" <hongru.zhr@alibaba-inc.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
X-Mailman-Version: 3.3.10
Precedence: list
Reply-To: "刘大鹏(鹏成)" <max.ldp@alibaba-inc.com>
Subject: [OAUTH-WG] 回复:draft-liu-oauth-authorization-evidence-02: an approver-side signature for 9.4
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/GmKE3c79_SYg6u67lPViOq2L_Eo>
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 Mohamad,
Thanks for the comments.
The draft does not define a mechanism for approver-side signatures. Section 9.4 makes the recommendation and deliberately leaves the mechanism open. If the WG sees a need for one, the draft could specify requirements for such signatures or reference existing IETF work.
At this stage, I think the priority is convergence within the WG on the evidence approach: both the problem statement and the evidence model.
Happy to discuss further. I can add you to the GitHub repository if you would like to collaborate there.
Regards,
Dapeng
------------------------------------------------------------------
发件人:Mohamad Khalil Yossif <mohamad@yuthent.com>
发送时间:2026年11月10日(周二) 00:23
收件人:oauth<oauth@ietf.org>
抄 送:"刘大鹏(鹏成)"<max.ldp@alibaba-inc.com>; "朱红儒(茱滴)"<hongru.zhr@alibaba-inc.com>; Suresh Krishnan<suresh.krishnan@gmail.com>; aaron<aaron@parecki.com>
主 题:draft-liu-oauth-authorization-evidence-02: an approver-side signature for 9.4
 Dapeng, Hongru, Suresh, Aaron,
Section 9.4 says the as_signature proves the AS recorded an approval,
not that the approver made it, and that deployments needing more SHOULD
add approver-side signatures. Laurent Lemonnier showed the case on the
AUDIT list this week: a server that signed a text the person had not
been shown still passed the -02 checks, and only the person's own
signature caught it.
draft-yossif-psea is one way to produce that signature. It is an EAT
profile in RATS: the approver's enrolled authenticator signs, after user
verification, over the SHA-256 of RFC 8785 bytes. If those bytes are the
disclosure object's JCS form, the approver signs what the AS records it
showed. An optional member of authorization_evidence could carry that
token, and a verifier compares its digest with the disclosure's.
It does not close 9.5. PSEA keeps trusted display out of scope, so it
proves the approver's key signed the bytes, not what the screen showed.
If this is useful, I can send proposed text for the optional member and
a worked example against Appendix B.
Mohamad