feat: add custom rate limiting for login/signup flow#1881
Open
S-MOHAMMED-ISMAIL wants to merge 3 commits into
Open
feat: add custom rate limiting for login/signup flow#1881S-MOHAMMED-ISMAIL wants to merge 3 commits into
S-MOHAMMED-ISMAIL wants to merge 3 commits into
Conversation
|
@S-MOHAMMED-ISMAIL is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
Contributor
Author
|
Implemented the requested rate limiting changes for authentication routes and verified that all CI checks are passing. Looking forward to feedback. Thanks! |
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
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.
Summary
Implemented custom rate limiting for authentication endpoints to provide additional protection against brute-force and excessive login/signup requests.
Closes #1851
Type of Change
Changes Made
Added rate limiting to authentication routes
Applied middleware protection to:
/api/auth/signin/api/auth/callbackReused the existing rate limiting infrastructure already used by other API endpoints
Returns HTTP
429 Too Many Requestswhen limits are exceededIncludes
Retry-Afterresponse headersUses separate limits for authenticated and anonymous users
How to Test
/api/auth/signin429response is returned after exceeding the limitRetry-Afterheader is present in the responseScreenshots (if UI change)
N/A
Checklist
npm run lintpasses locallyAdditional Notes
This change brings login/signup security in line with other rate-limited endpoints in DevTrack and helps reduce the risk of brute-force authentication attempts.