Explicit jackson serializer for jwt token provider #7580
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Description
JJWT current version has a very inefficient lookup implementation. This can lead to unexpected outcomes, ultimately resulting on the
io.jsonwebtoken.io.Serializer: Error accessing configuration fileissue.Adding an explicit serializer is enough to bypass the lookup and avoid the issue completely (see https://github.com/jwtk/jjwt/blob/0.11.5/impl/src/main/java/io/jsonwebtoken/impl/DefaultJwtBuilder.java#L287-L292).
I believed they have fixed this in version 0.12 but it is still under development.
Fixed Issue(s)
fixes #7559
Documentation
doc-change-requiredlabel to this PR if updates are required.Changelog