[THREESCALE-11474] JWT signature verification, support for ES256/ES512 #1533
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
https://issues.redhat.com/browse/THREESCALE-11474
Notes
Due to lua-resty-jwt is somewhat abandon, we need to rebuild lua-resty-jwt to include the authentication bypass fix
Verification steps:
admin
and password:adminpass
basic
realm, thenclients -> my-client -> Advanced
Access token signature algorithm
to ES256, then clickSave
"alg": "ES256"
Access token signature algorithm
to ES512, then clickSave