FEAT: 리프레시 토큰 구현 #84
Merged
FEAT: 리프레시 토큰 구현 #84
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
humpose
reviewed
Nov 6, 2024
| private final UserService userService; | ||
|
|
||
| @PostMapping("/refresh") | ||
| public ResponseEntity<TokenResponseDTO> refreshToken(@RequestBody RefreshTokenRequestDTO refreshTokenRequestDTO){ |
There was a problem hiding this comment.
혹시 여기에서 refreshTokenRequestDTO의 멤버인 refreshToken이 기존의 토큰을 가리키는 것이 맞나요?
There was a problem hiding this comment.
제가 질문을 잘 이해 못했는데 기존 access토큰 하나만 발급하던 로직에서 이제 access token과 refresh token둘 다 발급합니다. 여기서는 카카오 refresh token이 아닌 자체 jwt refresh token입니다
humpose
previously approved these changes
Nov 6, 2024
jjh4450
approved these changes
Nov 6, 2024
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.
loginUser 로직 변경과 리프레시 토큰구현을 완료하였습니다
또한 유저정도 update api도 구현 하였습니다
블랙리스트 기능은 개발중입니다