[#81] JWT 토큰으로 유저 정보 가져오도록 수정 #85
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
|
OMG |
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.
#️⃣ 연관된 이슈
Resolves #81
📝 작업 내용
@AuthenticationPrincipal을 이용하여 임시로 userId를 직접 사용하던 기존의 방식을 jwt 토큰으로 유저의 정보를 가져오는 방식으로 수정했습니다!
로그인 시 accessToken과 refreshToken을 확인할 수 있습니다. accessToken으로 인증을 진행하면 userId를 직접 입력하지 않아도 해당 유저의 정보들을 기반으로 기능들이 동작합니다.
스크린샷 (선택)
💬 리뷰 요구사항(선택)
✅ Check List