We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently ejabberd errors out if you provide multiple keys for jwt auth.
It would be nice, to have support to verify any key based on jwt auth best practice, as this would allow key rotation,
ejabberd/src/ejabberd_options.erl
Line 470 in c291c20
It should be able to read multiple keys, select the correct key and verify the token based on kid.
The new way of doing things is to accept a url and query it to find list of keys and to validate based on those keys
Sources:
https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets https://stytch.com/blog/understanding-jwks/
Edit: Added sources
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently ejabberd errors out if you provide multiple keys for jwt auth.
It would be nice, to have support to verify any key based on jwt auth best practice, as this would allow key rotation,
ejabberd/src/ejabberd_options.erl
Line 470 in c291c20
It should be able to read multiple keys, select the correct key and verify the token based on kid.
The new way of doing things is to accept a url and query it to find list of keys and to validate based on those keys
Sources:
https://auth0.com/docs/secure/tokens/json-web-tokens/json-web-key-sets
https://stytch.com/blog/understanding-jwks/
Edit: Added sources
The text was updated successfully, but these errors were encountered: