| Internet-Draft | Client Assertion Auth Redux | March 2025 |
| Jones, et al. | Expires 22 September 2025 | [Page] |
TODO Abstract¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://bc-pi.github.io/7523redux/draft-campbell-oauth-rfc7523redux.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-campbell-oauth-rfc7523redux/.¶
Discussion of this document takes place on the Web Authorization Protocol Working Group mailing list (mailto:oauth@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/oauth/. Subscribe at https://www.ietf.org/mailman/listinfo/oauth/.¶
Source for this draft and an issue tracker can be found at https://github.com/bc-pi/7523redux.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 22 September 2025.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
TODO Introduction that mentions [AUDIENCE-TAKES-SHOW] and mayby a bit of context/history and motivation for this doc that will update/patch [RFC7523], [RFC7522], and [RFC9126].¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
aud must solely contain the authorization server's issuer identifier.¶
Explicit typing of the Client Authentication JWT as a good thing to do in general but also allowing for observerability and controle during the transition period.¶
This hasn't been used in practice and this document will say not to ever use it going forward.¶
This specification tightens assertion audience handling directives as a mitigation for potential attacks arising from the exploitation of ambiguities in authorization server identification allowed by [RFC7523], [RFC7522], [RFC7521], and compounded by [RFC9126].¶
IANA is requested to update the "OAuth URI" registry [IANA.OAuth.Parameters] for the following entriest to add [[this specfication]] as an addtional refernce:¶
Registration is requested for the following media type in the IANA "Media Types" registry [IANA.MediaTypes] in the manner described in [RFC6838].¶
TODO for application/client-authentication+jwt¶
[[ to be removed by the RFC Editor before publication as an RFC ]]¶
draft-campbell-oauth-rfc7523redux-00:¶
Initial draft proposing a simipler and less distrupitve alternative to [I-D.ietf-oauth-rfc7523bis]¶
The authors would like to acknowledge the following people for their contributions to this document: John Bradley, Ralph Bragg, Joseph Heenan, Pedram Hosseyni, Aaron Parecki, Filip Skokan, and Tim Würtele.¶