fix: explicitly specify HS256 algorithm for JWT signing#150
Merged
LivingLikeKrillin merged 1 commit intodevelopfrom Mar 27, 2026
Merged
fix: explicitly specify HS256 algorithm for JWT signing#150LivingLikeKrillin merged 1 commit intodevelopfrom
LivingLikeKrillin merged 1 commit intodevelopfrom
Conversation
jjwt의 signWith(key)가 키 길이에 따라 알고리즘을 자동 선택하여 NimbusJwtDecoder(HS256 고정)와 불일치하는 문제 수정 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
1 participant
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
signWith(key)가 키 길이에 따라 알고리즘을 자동 선택(HS384/HS512)하여NimbusJwtDecoder(HS256 고정)와 불일치하는 문제 수정signWith(getSigningKey(), Jwts.SIG.HS256)으로 알고리즘 명시Test plan
🤖 Generated with Claude Code