-
Notifications
You must be signed in to change notification settings - Fork 2
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
수정 : 로그인 인증 예외 핸들러 적용 및 JWT 예외 반환 로직 수정 #112
Conversation
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.
원인 찾느라 고생하셨습니다!! 남긴 리뷰 몇가지만 확인해보시면 될 것 같아요!
public void validateToken(String token) { | ||
Jwts.parserBuilder().setSigningKey(key).build().parseClaimsJws(token); |
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.
코드가 이렇게 수정되면 더 이상 validateToken
네이밍은 아닐 것 같은데 어떻게 생각하시나용!??
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.
140ef5f 피드백 반영
- 파싱 메소드 자체가 좀 중복되어어서 로직을 변경하였습니다.
- 해당 메소드는 삭제하였고 parseClaims 메소드에서 일괄적으로 수행합니다 !
@ResponseStatus(UNPROCESSABLE_ENTITY) | ||
public ErrorResponse handleUnexpectedException(BadCredentialsException e) { | ||
log.warn("BadCredentialException Occurs : {}", e.getMessage()); | ||
public ErrorResponse handleUnexpectedException(AuthenticationException e) { |
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.
메서드 이름이 이상한 것 같아요!~!
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.
0aff2bd 커밋 피드백 반영
- 앗 메소드 네이밍 수정하였습니다 ㅎㅎ
🔍 어떤 PR인가요?
😋 To Reviewer