Re: [OAUTH-WG] JWK Thumbprint URI Specification

[David Chadwick <[e-mail]>]

Yes this will work for SIOPv2 that is sending VPs as JWKs, because they can use the "sub_jwk" claim to send the public key parameters as you say. Thanks

David

On 24/11/2021 21:18, Mike Jones wrote:

The JWK Thumbprint is typically used as a key identifier. Yes, the key needs to be known by other means if you’re going to use it.  Some protocols work that way, which is what this spec is intended to enable.  For instance, the Self-Issued OpenID Provider (SIOP) v1 and v2 protocols send the public key separately in a “sub_jwk” claim.  In other use cases, it may already be known to the receiving party – for instance, from a prior discovery step.

 

It would be fine to separately also define a URI representation communicating an entire JWK, but that would be for different use cases, and not the goal of this (intentionally narrowly scoped) specification.

 

                                                       Cheers,

                                                       -- Mike

 

From: OAuth <[e-mail]> On Behalf Of David Chadwick
Sent: Wednesday, November 24, 2021 12:36 PM
To: [e-mail]
Subject: Re: [OAUTH-WG] JWK Thumbprint URI Specification

 

On 24/11/2021 20:07, Mike Jones wrote:

The JSON Web Key (JWK) Thumbprint specification [https://www.rfc-editor.org/rfc/rfc7638.html" rel="nofollow">RFC 7638] defines a method for computing a hash value over a JSON Web Key (JWK) [https://www.rfc-editor.org/rfc/rfc7517.html" rel="nofollow">RFC 7517] and encoding that hash in a URL-safe manner. https://twitter.com/kristinayasuda" rel="nofollow">Kristina Yasuda and I have just created the https://www.ietf.org/archive/id/draft-jones-oauth-jwk-thumbprint-uri-00.html" rel="nofollow">JWK Thumbprint URI specification, which defines how to represent JWK Thumbprints as URIs. This enables JWK Thumbprints to be communicated in contexts requiring URIs, including in specific JSON Web Token (JWT) [https://www.rfc-editor.org/rfc/rfc7519.html" rel="nofollow">RFC 7519] claims.

 

My immediate observation is why are you sending the thumbprint of the JSON Web Key and not sending the actual key value in the URI?

Sending the thumbprint means the recipient still has to have some other way of obtaining the actual public key, whereas sending the public key as a URI means that no other way is needed.

Kind regards

David

 

Use cases for this specification were developed in the https://openid.net/wg/connect/" rel="nofollow">OpenID Connect Working Group of the OpenID Foundation. Specifically, its use is planned in future versions of the https://openid.net/specs/openid-connect-self-issued-v2-1_0.html" rel="nofollow">Self-Issued OpenID Provider v2 specification.

 

The specification is available at:

1.       https://www.ietf.org/archive/id/draft-jones-oauth-jwk-thumbprint-uri-00.html" rel="nofollow">https://www.ietf.org/archive/id/draft-jones-oauth-jwk-thumbprint-uri-00.html

 

                                                       -- Mike

 

P.S.  This note was also published at https://self-issued.info/?p=2211" class="moz-txt-link-freetext" rel="nofollow"> https://self-issued.info/?p=2211 and as https://twitter.com/selfissued/" rel="nofollow"> @selfissued.

 

_______________________________________________

OAuth mailing list

[e-mail]

https://www.ietf.org/mailman/listinfo/oauth" class="moz-txt-link-freetext" rel="nofollow">https://www.ietf.org/mailman/listinfo/oauth