[DP-306] Refresh Token rotation 제거로 로그인 튕김 현상 수정#121
Merged
nYeonG4001 merged 1 commit intodevelopV2from Apr 12, 2026
Merged
Conversation
|
nYeonG4001
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
문제
액세스 토큰 만료(1시간) 시 프론트에서 여러 API가 동시에 401을 받으면,
/auth/refresh요청이 동시에 여러 번 발생.Token Rotation 방식에서 첫 번째 요청이 기존 refresh token을 DB에서 삭제하고 새 토큰을 생성하면, 이후 요청들은 이미 삭제된 토큰으로 재발급을 시도해 401 → 로그아웃 처리되는 레이스 컨디션 발생.
원인
TokenService.reissueTokens()에서 Token Rotation(기존 토큰 삭제 + 새 토큰 발급) 수행 시 동시 요청에 취약수정 내용
영향 범위
TokenService.reissueTokens()TokenServiceTest