[FIX] JWT 미지원 Subject 검증 보완 - #577
Draft
GiJungPark wants to merge 1 commit into
Draft
Conversation
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.
Related Issue
Key Changes
ACCESS,REFRESH, 미지원 값으로 명시적으로 구분하도록 검증 로직을 보완했습니다.UNSUPPORTED_SUBJECT로 판별하도록 처리했습니다.UNSUPPORTED_SUBJECT를 기존INVALID_TOKEN(AUTH-001, 401) 응답으로 처리하고 필터 체인을 중단하도록 했습니다.UNSUPPORTED_TOKEN동작은 유지했습니다.To Reviewers
AUTH-001로 응답하도록 구현했습니다.References