Refactor security/jwt
in order to use JWT builder inside a Quarkus application
#664
+120
−114
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.
Summary
quarkus-smallrye-jwt-build
is using a private RSA key in order to sign generated JWT tokens. This private key could be read just by setting the propertysmallrye.jwt.sign.key.location
.This PR creates a
/login/jwt
endpoint in order to verify the extensionquarkus-smallrye-jwt-build
inside a Quarkus application.Please select the relevant options.
Checklist: