Throtter#864
Merged
Merged
Conversation
|
@Nanafancy is attempting to deploy a commit to the naijabuz's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@Nanafancy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
yusuftomilola
approved these changes
Jun 1, 2026
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.
[BE-29] Add global ThrottlerGuard for rate limiting in opsce module
Problem
@nestjs/throttler is installed but not configured. All endpoints are open to brute-force attacks. The login endpoint is especially vulnerable to credential stuffing.
Proposed Solution
Configure ThrottlerModule.forRootAsync() in OpsceModule. Apply stricter per-route limits on /api/auth/login and /api/auth/forgot-password.
Acceptance Criteria
Global limit: 100 requests per 60 seconds per IP
POST /api/auth/login limited to 5 requests per 60 seconds per IP using @Throttle()
POST /api/auth/forgot-password limited to 3 requests per 60 seconds per IP
Returns 429 Too Many Requests with Retry-After header when limit is exceeded
TTL and limit values configurable via THROTTLE_TTL and THROTTLE_LIMIT env variables
Guard registered globally via APP_GUARD in OpsceModule
closes #754