You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it looks like PyJWKClient relies on this param to work at all, why not make it the default to include kid in the JWT headers?
If the field is empty or null, the JWK client will never match the key.
I realize kid is an optional field, but its useful and it would make sense to me to include it, as otherwise the client that comes with the library doesn't even work with JWT tokens signed by this library - which seems inconsistent.
So it looks like
PyJWKClient
relies on this param to work at all, why not make it the default to includekid
in the JWT headers?If the field is empty or null, the JWK client will never match the key.
I realize
kid
is an optional field, but its useful and it would make sense to me to include it, as otherwise the client that comes with the library doesn't even work with JWT tokens signed by this library - which seems inconsistent.More info on
kid
aka `key id" field: https://datatracker.ietf.org/doc/html/rfc7517#section-4.5Andhere in a more user friendly format: https://fusionauth.io/articles/tokens/jwt-components-explained
The text was updated successfully, but these errors were encountered: