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

Refactor security/jwt in order to use JWT builder inside a Quarkus application #664

Merged
merged 1 commit into from
Jun 1, 2022

Conversation

pjgg
Copy link
Contributor

@pjgg pjgg commented May 30, 2022

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 property smallrye.jwt.sign.key.location.

This PR creates a /login/jwt endpoint in order to verify the extension quarkus-smallrye-jwt-build inside a Quarkus application.

Please select the relevant options.

  • New scenario (non-breaking change which adds functionality)

Checklist:

  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@pjgg pjgg requested a review from jsmrcka May 30, 2022 11:07
@pjgg pjgg force-pushed the feat/jwt_update branch from 147aac8 to 2b96997 Compare May 30, 2022 11:13
@pjgg pjgg added triage/backport-2.2? triage/backport-2.7? It needs to backport changes to branch 2.7 and removed triage/backport-2.2? labels May 31, 2022
@pjgg pjgg force-pushed the feat/jwt_update branch from 2b96997 to c90514b Compare May 31, 2022 17:17
@pjgg pjgg requested a review from jsmrcka May 31, 2022 17:19
@jsmrcka jsmrcka merged commit 388fb8d into quarkus-qe:main Jun 1, 2022
@pjgg pjgg mentioned this pull request Jun 6, 2022
2 tasks
@pjgg pjgg added this to the 2.7 milestone Jun 8, 2022
@pjgg pjgg removed the triage/backport-2.7? It needs to backport changes to branch 2.7 label Jun 8, 2022
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

Successfully merging this pull request may close these issues.

2 participants