Fix: Cors Header added and allowed Origins specified#22
Merged
Conversation
arnaudfnr
force-pushed
the
arnaudfnr/fix-auth-JWT
branch
from
7a65675 to
02c6e6c
Compare
Cabanon
approved these changes
Feb 6, 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
2 participants
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.
Fix missing CORS settings in backend to allow requests from frontend.
I put token endpoints under the prefix
authfor more clarity.I added
auth/verifyendpoint to be able to check validity of stored token from frontend side.Added some dummy tests on webapp to check viability of fix (TO BE REMOVED).