Next auth 구현 및 fetch 추상화 개선 #40
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
auto-assign
bot
requested review from
punchdrunkard,
saseungmin,
seokzin and
Zero-1016
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Closed
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.
PR 타입 ( 하나 이상의 PR 타입을 선택해주세요 )
변경 사항
next-auth를 이용해서 Next 서버단에서 카카오 유저정보를 가져와서 서버쪽에 바로 넘겨주고AccessToken, RefreshToken, isProfileRegistered를 Session에 담아서
커스텀한 fetch 헤더에 토큰을 담아 실어보내고 있습니다.
middleware를 auth로 감싸서 매 요청마다 거치게 되는데 이때,
jwtexp 를 확인해서 refresh를 진행해줍니다.