I suggest that JWK::parseKey() be made public

[csev]

There are situations where we want to parse a key that is not always part of a keyset. Perhaps we stored the key in session or in a database - or perhaps in a unit test.

[bshaffer]

@csev You can always call JWK::parseKeySet(['keys' => [$key]]);, so I don't understand why it is necessary to make parseKey public.

[csev]

Thanks - that makes a lot of sense. It is good enough for me.

[simonknittel]

I've just stumbled upon an implementation in which the JWT doesn't contain a kid. Therefore decode wasn't able to find the correct key within the JWKS. Being able to directly call parseKey would help here.

[kamazee]

Same here.
To get a single key, JWT::parseKeySet(['keys' => [getkey($id)]])[$id] is required instead of just JWT::parseKey(getKey($id)); (where getKey($id) is a function that returns a key by its ID that is passed in a JWT header)
While the former is indeed possible, it's clearly quite a mental roundtrip while the latter shows the intent pretty clearly.

@bshaffer , any chance to reconsider? 🙄

[bshaffer]

I can't see an issue with making it public if there's a use-case for it