Implement challenge rate limiting and session revocation checks in auth routes#671
Open
somotochukwu-dev wants to merge 1 commit into
Open
Implement challenge rate limiting and session revocation checks in auth routes#671somotochukwu-dev wants to merge 1 commit into
somotochukwu-dev wants to merge 1 commit into
Conversation
|
@Dubemtopsite is attempting to deploy a commit to the mAzI's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@somotochukwu-dev 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! 🚀 |
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
Implements per-IP rate limiting for the challenge creation endpoint, fixes broken code in the auth router, adds DI support for testability, and enforces strict 401 on auth failures.
Changes
backend/src/routes/auth.tsPOST /challenge, keyed by client IP viax-forwarded-for. Idle buckets pruned every 60s to prevent memory leaks./verifyhandler block. Properly closedextractSignatureStringfunction. Removed dead duplicatedecodeSignature.createAuthRouter(deps): New DI-enabled factory returning an Express Router that uses injectedprismaClientandredisClient. All routes (challenge, verify, refresh, logout, session) wired through DI.isSessionRevoked(redisClient, token): Exported function for session blacklist lookup with 1msPromise.racetimeout.validateStellarAddress(raw): Returns{valid, address|error}for granular error messages (format vs checksum).sanitizeStellarAddress: Removed.trim().toUpperCase()normalization — now validates exact input.validateStellarAddressfor descriptive errors.backend/tests/auth.test.ts$transaction,refresh_tokensmocks to DI prisma client.anyannotations on mock callbacks.process.env.JWT_SECRETfor integration router test.tests/e2e/auth.test.tsbackend/package.jsonscriptsobject preventednpm install).Acceptance Criteria Verification
verifyStellarSignatureverifyhandler returns 401isChallengeFreshgate returns 401isSessionRevokedwith 1ms timeout raceAll 5 unit tests pass (
node --require ts-node/register --test tests/auth.test.ts).Closes #463