| Internet-Draft | TODO - Abbreviation | February 2025 |
| Richer, et al. | Expires 30 August 2025 | [Page] |
Sometimes you want to get a token that's tied to a public key but you can't prove possession of that public key. That's when you need to trust me, bruh.¶
This note is to be removed before publishing as an RFC.¶
The latest revision of this draft can be found at https://jricher.github.io/draft-richer-oauth-tmb-claim/draft-richer-oauth-tmb-claim.html. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-richer-oauth-tmb-claim/.¶
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/jricher/draft-richer-oauth-tmb-claim.¶
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 30 August 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.¶
The JWT confirmation claim "cnf" [RFC7800] allows an RS to determine PoP semantics for a token. However, methods like mTLS [RFC8705] and DPoP [RFC9449] assume that the requester of that token can prove possession of the key that is bound to the token. Sometimes that's just too hard, and so here we define a claim to allow a requester to ask for a token that is bound to a key that the requester cannot, does not want to, or does not feel like proving possession of at the time of request.¶
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.¶
The token meta-key binding "tmb" claim is passed in an OAuth token request parameter of the same name. Its value is the form-encoded value that the requester wants the confirmation claim to be in the issued token. If the requester is making a DPoP or mTLS request, any keys there MUST be ignored.¶
The same parameter can be used in a token exchange request, with the same results.¶
If the issued token is a JWT, the value of the "tmb" claim is copied to the "cnf" claim of the resulting token. If the token is introspected, the value of "tmb" is returned in the "cnf" claim of the introspection response.¶
The requester SHOULD give the resulting token to the holder of the key represented in the "tmb" claim.¶
The presenter of the token MUST prove possession of the key in the resulting "cnf" claim using the appropriate key validation method for the type of token.¶
The security of this specification is entirely based on trust. If you have trust issues, it's not going to be secure.¶
This document registers the "tmb" claim to the IANA JWT Claims registry and OAuth request parameter.¶
TODO acknowledge.¶