feat(backend): rate limit auth and CORS for creator FE - #281
Open
idowuvictor wants to merge 3 commits into
Open
Conversation
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
1 participant
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.
Description
This PR hardens the creator auth path by introducing rate limiting and CORS configuration for the frontend as requested in the issue.
Changes Made:
CORS_ORIGINSenvironment variable inmain.tsso the creator app can call the API safely in both local and production environments.@nestjs/throttlerto rate-limit the SEP-10 challenge and verify endpoints within the auth module to prevent wide-open abuse.README.mdandbackend/.env.exampleto document the setup forCORS_ORIGINSandNEXT_PUBLIC_API_URL.Closes #271