The order of selecting correct key to verify signature about jwx HOT 2 CLOSED

I'm not saying that it isn't, but at the same time I'm not convinced that what you suggest is an optimization, because I haven't been presented with evidence that most of times the kid will be present. I'm willing to be convinced otherwise. For the time being though, by reading the RFC and seeing the examples that are around in my view I determined that I could not optimize for the presence of kid, and that's why it's the way it is.

For your case, you are free to write your own optimized version of a KeyProvider that is optimized to your needs. I think this would solve your problems?

from jwx.

Thanks for a quick response @lestrrat.

I think that the performance penalty coming from iterating over all the keys and finding the matching kid is minimal compared to actual verification, but this is only my feeling :)

KeyProvider looks fine, it's good to know that there's a workaround available. Thanks!

from jwx.