Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding kid jwt header by default #976

Open
adamJLev opened this issue Aug 19, 2024 · 1 comment
Open

Consider adding kid jwt header by default #976

adamJLev opened this issue Aug 19, 2024 · 1 comment

Comments

@adamJLev
Copy link

adamJLev commented Aug 19, 2024

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.

More info on kid aka `key id" field: https://datatracker.ietf.org/doc/html/rfc7517#section-4.5
Andhere in a more user friendly format: https://fusionauth.io/articles/tokens/jwt-components-explained

@adamJLev adamJLev changed the title Why not embed kid by default? Consider adding kid jwt header by default Aug 19, 2024
@gagandeepp
Copy link
Contributor

interested @adamJLev please assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants