Configure AntiForgery in WebApp #295
Closed
Conversation
This file contains 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
tjementum
requested changes
Jan 15, 2024
raix
force-pushed
the
294-configure-antiforgery-in-webapp
branch
from
3541e8c to
54cfa4c
Compare
|
… endpoints except /api/track
tjementum
force-pushed
the
294-configure-antiforgery-in-webapp
branch
from
d46a964 to
0dcc784
Compare
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 & Motivation
We want to prevent cross-site request forgery (XSRF/CSRF) attacks.
This pull-request adds token exchange via runtime environment allowing the api client to send the token in headers.
We also add and configure the anti forgery middleware.
Checklist