Re: [jose] #16: URI identifying a specific key in a JWK set

["jose issue tracker" <[e-mail]>]

#16: URI identifying a specific key in a JWK set


Comment (by [e-mail]):

 First, having just a "jku" value is often sufficient to determine which
 key to use, as other parameters in the JWK Set such as the "use" or "alg"
 parameters may be used to unambiguously determine which key to use.  There
 may also be only one key in the set.

 Second, we already support more than one means of disambiguating keys
 within JWK Sets, including using the "kty", "kid", "use", and "alg" values
 as inputs to this decision.  And once the spec says that other fields must
 be ignored if not understood, I'm sure that people will use other key
 properties they'll invent such as ("current": true) to aid in the key
 selection process for their applications.

 I understand that the request may seem simple on the face of it, but doing
 this in a general way would involve more than just using a "kid" value as
 a fragment identifier for a "jku" value.  As such, the proposal seems
 underspecified to me.

 Furthermore, if all that's being conveyed is a "jku" value and a "kid"
 value pair - we already have a straightforward way of doing that - include
 both parameters in the header.  Whereas requiring implementations to
 support two ways of accepting the same information doesn't seem like a
 good cost/benefit tradeoff.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  [e-mail]    |  [e-mail]
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  key                    |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/16#comment:1>
jose <http://tools.ietf.org/jose/>