feat(notifications): add CORS allowlist enforcement on /api/notifications - #725
Merged
greatest0fallt1me merged 4 commits intoJul 29, 2026
Merged
Conversation
…ions - Added NOTIFICATIONS_CORS_ALLOWED_ORIGINS env variable to env schema - Added notificationsCors() factory in cors.ts middleware (deny by default) - Applied middleware to notificationsRouter before auth - Mocked CORS middleware in existing tests Closes Predictify-org#609
- Added missing RouteErrorFactory import - Fixed async error handling: use next() instead of throw in async handler - Fixed test assertion: expects 422 from RouteErrorFactory.validation - Removed fragile details assertion that didn't match actual error envelope
|
@Obaara293 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! 🚀 |
Contributor
|
Merged into main via admin resolver (-X theirs). |
Contributor
|
CI green, LGTM ✨ merged. |
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.
Overview
This PR adds CORS allowlist enforcement on
/api/notificationsto ensure only approved origins can make cross-origin requests (deny by default; preflight cached).Related Issue
Closes #609
Changes
Middleware
NOTIFICATIONS_CORS_ALLOWED_ORIGINSenvironment variable in env schemanotificationsCors()factory insrc/middleware/cors.ts— reads allowed origins from env, denies non-matching origins with 403, caches preflight OPTIONS responses for 600s viaAccess-Control-Max-AgeRoute
src/routes/notifications.ts— appliednotificationsCors()middleware as the first middleware on the router so unapproved origins are rejected before any processing occursRouteErrorFactoryimport that caused a crash on PATCH validation failurethrow RouteErrorFactory.validation(...)toreturn next(...)for proper async error handling in Express 4Tests
tests/notifications.test.ts— mocked the CORS middleware, fixed test assertions to match actual error envelope (422 +validation_errorcode)Verification Results
/api/notificationsNOTIFICATIONS_CORS_ALLOWED_ORIGINSenv; non-matching origins denied with 403NOTIFICATIONS_CORS_ALLOWED_ORIGINSis empty, all cross-origin requests are deniedAccess-Control-Max-Age: 600