Helpful explanation of a tricky issue that can easily trip people up when moving to GraalVM. Could future JJWT updates make this reflection setup unnecessary, or will manual config likely remain part of native image builds?
Upgrading JJWT on Spring Boot 3.3.x for GraalVM and Cloud Native
Ricardo Campos
posted
1 min read
3 Comments
Gimi
•
Thanks for documenting this. Reflection config issues with GraalVM are painful to debug when you hit them fresh.
What use case drove you toward native-image for this project? Startup time, memory footprint, or deployment constraints?
The supplier pattern change in 0.12.7 makes sense for flexibility but breaks classpath scanning at native compile time. Your config snippet handles the core builder suppliers. Did you run into any additional reflection gaps with custom claim types or key serializers beyond those four entries?
Hope to talk soon!
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- Premium Subscription
- Terms of Service
- Refund
- Early Builders
chevron_left
More From Ricardo Campos
Related Jobs
- Senior AWS Cloud EngineerDish · Full time · India
- Senior AWS Cloud EngineerDish · Full time · India
- Senior Enterprise Systems Engineer - Cloud & AIjobgether · Full time · India
Commenters (This Week)
buildbasekit
3 comments
BashSnippets
3 comments
Klajdi Murataj
2 comments
Contribute meaningful comments to climb the leaderboard and earn badges!