[OAUTH-WG] Weekly github digest (OAuth Activity Summary)

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 04 February 2024 07:40 UTC

Return-Path: <do_not_reply@mnot.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FED9C14F605 for <oauth@ietfa.amsl.com>; Sat, 3 Feb 2024 23:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.405
X-Spam-Level:
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=mnot.net header.b="bM8NKNQf"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b="dt5I+1bA"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUQGSnwKemnV for <oauth@ietfa.amsl.com>; Sat, 3 Feb 2024 23:40:31 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4207EC14CEFC for <oauth@ietf.org>; Sat, 3 Feb 2024 23:39:41 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8166B5C00EC for <oauth@ietf.org>; Sun, 4 Feb 2024 02:39:40 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 04 Feb 2024 02:39:40 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-type:content-type:date:from:from:in-reply-to :mime-version:reply-to:subject:subject:to:to; s=fm1; t= 1707032380; x=1707118780; bh=pcDjYOJopp+kgi6TgggLFpdysq6ZiVLyNy5 MgIlVFjA=; b=bM8NKNQfGUr7JIHs8p1IyBYQhNPVR9fbNGedjKKkqTHegCJw6HS JvINO90lemzy8Z758Sc2AFWmoQYm9TwJSZpRix52S/EjNRf1WJbTu7WWVtW0wUXG xYqlykWkVbvs7MNB2aGvuYfdcK7AmUuVgpR7H/+zobPG28RzvL3RI2WJs4+vOI0x nrQMEB6rZBCWTit0nQFKQrCAakIqJAdZMxgtD5dHwzZpdaaj4Od0web49a5pW484 LvPY/YBrRZFwzUYPvB1gAqG96Gsx4dMQVKSezU056EoNxke/vz2bg+aG8hrLQMlc NqTHMMqf3/xeGKS0ooUjDi2EFaVGzen/woQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date :feedback-id:feedback-id:from:from:in-reply-to:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1707032380; x= 1707118780; bh=pcDjYOJopp+kgi6TgggLFpdysq6ZiVLyNy5MgIlVFjA=; b=d t5I+1bAoIwf+uLXDdg+/wT2jHTS6cWnwqf867RqNidtUMIiy0e7rh13HEy/gw2uJ l6J31Oo1XqpTg1P30U7p2rZEWqSFP/zbnrLngDaHMGpeYDeFCQDKxlLw1OAkjcMg 9SeONXJPrflpde6Ljplstwh5CU6DucYRiWHcghNIFCPXSC/KBEVBmZlIyN+zrAqg 4yaHPzOPY84Cuhol7ouzy4MZPyJT+8Ak+5GV0lsENb2NicCNp51Xt9P3xxOFQM6F R5weCCrNdSrAltgSdhZjIVAjMSj5A0aVojX2n+JN7ARaUDVeHppHEHktn865kGTS nSY874igoS62ilmvpVY2A==
X-ME-Sender: <xms:PD-_ZaHI_YcqfkgdzObHb36QMFp2WTLjSfeNPAa6nPCZ8YyU06sVFQ> <xme:PD-_ZbUuscPxuZzVMlyZNAKNQbIOjFQQr2otWPL5Lt1AinQICavex_zMGumTcbjv3 _jdC3HuPoL7GqFHiA>
X-ME-Received: <xmr:PD-_ZULZo34iuRECLv5B1ko7AyXSUx03pAllvQbCEDc9QA_AcIIaPp38MOmNygBP>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrfedujedgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepgeenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:PD-_ZUE5sOpQJDjTGtTEQppm6NUMUawSFiZNEZLreRqFhP0xZkHzPA> <xmx:PD-_ZQWLqKJGTgTt9i1Mcs735IpdIbAsCvPC9HYZNOD40QQRGvDZJA> <xmx:PD-_ZXNLLK5rY69UNJoiCaiEAUlL-yJPiSOlpxwWA9mdj8uieW5OhQ> <xmx:PD-_ZTCjxuAXvB2CaWTqcsZSvYeFjmKY8VmJGq-hAywu_af4ZbMbJg>
Feedback-ID: i1c3946f2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <oauth@ietf.org>; Sun, 4 Feb 2024 02:39:40 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============5419298023694234931=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: oauth@ietf.org
Message-Id: <20240204073941.4207EC14CEFC@ietfa.amsl.com>
Date: Sat, 03 Feb 2024 23:39:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/GwwdCmNFJWQoUW1NKIKREL3LntQ>
Subject: [OAUTH-WG] Weekly github digest (OAuth Activity Summary)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Feb 2024 07:40:32 -0000



Events without label "editorial"

Issues
------
* oauth-wg/oauth-identity-chaining (+0/-4/💬5)
  5 issues received 5 new comments:
  - #69 Add Aaron Parecki to acknowledgements section (1 by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/issues/69 
  - #67 Change spec name to focus on Authz (1 by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/issues/67 
  - #61 authorization grant type can't be the same as the issued token type (1 by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/issues/61 
  - #60 example response missing issued_token_type (1 by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/issues/60 
  - #45 Consider limiting token formats to JWT (1 by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/issues/45 

  4 issues closed:
  - Add Aaron Parecki to acknowledgements section https://github.com/oauth-wg/oauth-identity-chaining/issues/69 
  - authorization grant type can't be the same as the issued token type https://github.com/oauth-wg/oauth-identity-chaining/issues/61 
  - example response missing issued_token_type https://github.com/oauth-wg/oauth-identity-chaining/issues/60 
  - Consider limiting token formats to JWT https://github.com/oauth-wg/oauth-identity-chaining/issues/45 

* oauth-wg/oauth-transaction-tokens (+2/-11/💬22)
  2 issues created:
  - Do we still need replacement transaction tokens. (by PieterKas)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/69 
  - Trust domain/audience claim format URI or StringOrUri? (by obfuscoder)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/66 

  9 issues received 22 new comments:
  - #69 Do we still need replacement transaction tokens. (1 by PieterKas)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/69 
  - #63 audience REQUIRED for just one trust domain? (4 by gffletch, obfuscoder, tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/63 
  - #62 Long-living Access Token needed for internal batch processes/offline tasks? (4 by gffletch, obfuscoder, tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/62 
  - #58 Authorization details presentation and processing (1 by tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/58 [PR57] 
  - #56 RFC 9493 and sub_id formats (3 by obfuscoder, tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/56 [PR57] 
  - #53 Transaction Tokens for S2S calls (5 by dteleguin, obfuscoder, tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/53 
  - #52 Should the azd claim be mandatory or optional (1 by tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/52 [pre-adoption] 
  - #35 How do internal services authorize the Transaction Tokens? (2 by obfuscoder, tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/35 
  - #21 Txt token Header  (1 by obfuscoder)
    https://github.com/oauth-wg/oauth-transaction-tokens/issues/21 

  11 issues closed:
  - Trust domain/audience claim format URI or StringOrUri? https://github.com/oauth-wg/oauth-transaction-tokens/issues/66 
  - audience REQUIRED for just one trust domain? https://github.com/oauth-wg/oauth-transaction-tokens/issues/63 
  - "sender constrained" language needs improvement https://github.com/oauth-wg/oauth-transaction-tokens/issues/48 
  - Txt token Header  https://github.com/oauth-wg/oauth-transaction-tokens/issues/21 
  - How do internal services authorize the Transaction Tokens? https://github.com/oauth-wg/oauth-transaction-tokens/issues/35 
  - RFC 9493 and sub_id formats https://github.com/oauth-wg/oauth-transaction-tokens/issues/56 [PR57] 
  - Should the azd claim be mandatory or optional https://github.com/oauth-wg/oauth-transaction-tokens/issues/52 [pre-adoption] 
  - Authorization details presentation and processing https://github.com/oauth-wg/oauth-transaction-tokens/issues/58 [PR57] 
  - Use of `actor_token` and `actor_token_type` https://github.com/oauth-wg/oauth-transaction-tokens/issues/60 [PR57] 
  - How is the `purp` claim of the Txn-Token defined? https://github.com/oauth-wg/oauth-transaction-tokens/issues/61 [PR57] 
  - Using Txn-Tokens securely https://github.com/oauth-wg/oauth-transaction-tokens/issues/49 [pre-adoption] 

* oauth-wg/oauth-sd-jwt-vc (+1/-0/💬3)
  1 issues created:
  - metadata path description (by c2bo)
    https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/203 

  1 issues received 3 new comments:
  - #203 metadata path description (3 by bc-pi)
    https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/203 



Pull requests
-------------
* oauth-wg/oauth-identity-chaining (+3/-4/💬1)
  3 pull requests submitted:
  - use more specific term "JWT authorization grant" (by aaronpk)
    https://github.com/oauth-wg/oauth-identity-chaining/pull/74 
  - Renamed the "Authorization Grant" header to "Access Token Request" (by aaronpk)
    https://github.com/oauth-wg/oauth-identity-chaining/pull/73 
  - limit authorization grant format to RFC7523 JWT  (by bc-pi)
    https://github.com/oauth-wg/oauth-identity-chaining/pull/72 

  1 pull requests received 1 new comments:
  - #73 Renamed the "Authorization Grant" header to "Access Token Request" (1 by aaronpk)
    https://github.com/oauth-wg/oauth-identity-chaining/pull/73 

  4 pull requests merged:
  - use more specific term "JWT authorization grant"
    https://github.com/oauth-wg/oauth-identity-chaining/pull/74 
  - More specific headers
    https://github.com/oauth-wg/oauth-identity-chaining/pull/73 
  - Added acknowledgement for Aaron Parecki
    https://github.com/oauth-wg/oauth-identity-chaining/pull/71 
  - limit authorization grant format to RFC7523 JWT 
    https://github.com/oauth-wg/oauth-identity-chaining/pull/72 

* oauth-wg/oauth-transaction-tokens (+4/-5/💬0)
  4 pull requests submitted:
  - clarified that aud claim should have the same format as in the JWT spec (by tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/70 
  - removed sender constrained text as discussed on 12/08 (by tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/68 
  - Clarify and align audience claim value format (by obfuscoder)
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/67 
  - updated HTTP reference (by tulshi)
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/65 

  5 pull requests merged:
  - clarified that aud claim should have the same format as in the JWT spec
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/70 
  - removed sender constrained text as discussed on 12/08
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/68 
  - updated HTTP reference
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/65 
  - Token exchange profile update
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/57 
  - Add header
    https://github.com/oauth-wg/oauth-transaction-tokens/pull/64 

* oauth-wg/oauth-sd-jwt-vc (+1/-0/💬0)
  1 pull requests submitted:
  - Fix inconstancy in the well-known path construction (by bc-pi)
    https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/204 

* oauth-wg/draft-ietf-oauth-resource-metadata (+0/-1/💬0)
  1 pull requests merged:
  - fix bearer_methods_supported
    https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata/pull/22 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/oauth-wg/oauth-browser-based-apps
* https://github.com/oauth-wg/oauth-identity-chaining
* https://github.com/oauth-wg/oauth-transaction-tokens
* https://github.com/oauth-wg/oauth-sd-jwt-vc
* https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata
* https://github.com/oauth-wg/oauth-cross-device-security
* https://github.com/oauth-wg/oauth-selective-disclosure-jwt
* https://github.com/oauth-wg/oauth-v2-1
* https://github.com/oauth-wg/oauth-browser-based-apps