Bucket4j를 이용한 과도한 RefreshToken 발행 요청 제한 - #112
Merged
yeomin4242 merged 9 commits intoJan 13, 2026
Merged
Conversation
minwoonggi
approved these changes
Jan 13, 2026
minwoonggi
left a comment
minwoonggi
left a comment
Contributor
There was a problem hiding this comment.
refresh관련 트래픽만 제한하는 것이었군요 잘봤습니다.
테스트 코드도 봤는데 통과가 다 됬다면 성공적으로 동작하겠네요
Member
Author
기본적으로 운영단계에서 fail2Ban이 동작해서 큰 틀에서 문제는 없을거 같아요 |
yeomin4242
deleted the
be/dev/feat-rate-limit-for-issue-refresh-token#111
branch
January 13, 2026 14:50
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
2 participants
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.
#️⃣연관된 이슈
#11
📝작업 내용
로그인 이후 사용자로부터 과도한 RefreshToken 재발급 요청에 대해서 처리하기 위해서
Bucket4j를 이용해서 1분당 요청 10회의 제한을 두어서 처리하고자 합니다.
스크린샷 (선택)
💬리뷰 요구사항(선택)