Bug: `gatewayRoutes` returns 500 instead of 401 when API key prefix exists but hash mismatches

[greatest0fallt1me]

Description

When a valid prefix is matched but the hash comparison fails, the gateway throws inside apiKeyRepository and surfaces as a 500. The correct response is a 401 with a generic message and no timing oracle.

Requirements and Context

• Wrap the hash compare in a constant-time path returning a typed InvalidKey error
• Update gateway handler to map to UnauthorizedError
• Add Jest test for the exact mismatch path
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b bug/gateway-prefix-hash-mismatch

2. Implement changes
   • src/repositories/apiKeyRepository.ts
   • src/routes/gatewayRoutes.ts
3. Test and commit
   • npm test -- gatewayRoutes
   • Cover edge cases (constant-time path verified)
   • Include test output and notes in the PR

Example commit message

fix: gateway returns 401 on hash mismatch

Acceptance Criteria

• Mismatch returns 401 not 500
• No timing oracle observable in test
• Tests cover both happy and mismatch paths
• Docs updated

Guidelines

• Backend (Node/TS): Jest, minimum 90% coverage
• Clear documentation and inline comments
• Timeframe: 96 hours

[Riel101]

hi, i can fix this for you

[Biokes]

@Biokes has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer,
I will like to work on this issue and get this fixed.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Biokes to this issue.

[grantfox-oss]

🦊 GrantFox — @Riel101 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #421)
2. Your PR will be reviewed by the CalloraOrg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

⚠️ @greatest0fallt1me: @Riel101 has been unassigned because this issue is part of the Stellar Wave Program, and @Riel101 doesn't have a pending application for this issue.

Contributors can apply through Drips Wave to be eligible for assignment and points. To assign a contributor outside of Wave to this issue, please first remove this issue from all Wave Programs.

[drips-wave]

Congratulations, @Biokes! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Biokes: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊