Refactor/83-스프링 시큐리티를 전체 API에 적용하기 #84
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
2 tasks
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.
🚀 개요
🔍 변경사항
@RequestHeader를 이용한 JWT 토큰을 직접 검사하는 방식 삭제@AuthMember를 이용해 현재 로그인 된 유저의 정보를 불러와 비즈니스 로직(서비스)에 사용⏳ 작업 내용
📝 논의사항
/reissue 동작 관련 서비스 코드를 개선하고자 하는데 Redis 붙일 때 같이 해도 괜찮을까요?