-
Notifications
You must be signed in to change notification settings - Fork 692
TOMEE-2515 MicroProfile JWT 1.1 Cleanup #465
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
Conversation
…rification" key "IssuedBy" becomes "issuer" to more directly map to the JWT
… isn't a request context object, but app scoped configuration.
Make it clearer that this is equivalent to JWTAuthConfiguration but created via MP-JWT standard properties.
|
|
||
| private Map<String, Key> signerKeys; | ||
| private String issuedBy; | ||
| private Map<String, Key> publicKeys; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not so sure about this one.
Key is the base class and can be a public key or a secret key.
What about signingKey?
It would be valid for either symmetric or asymmetric key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to "verificationkey" most places
… Favor "verificationKey" over "publicKey" when possible.
Still not wired up to an interceptor
…ional. Needs tests, logging and documentation
Will come back and attempt to fix builder pattern in JsonWebTokenValidator
|
Merging so we can get a build from the CI and move forward with the 8.0.0-M3 release |
Still in the trimming code stage. Plan to get on to logging improvements and greater tests shortly.