TestCsrfTokenRepository should delegate to the configured CsrfTokenRepository #13082
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.
I'm creating this as a draft, because there are some failing tests I need to fix before this can be merged.
CsrfRequestPostProcessor
currently reconfiguresCsrfFilter
with aTestCsrfTokenRepository
that delegates to a newly createdHttpSessionCsrfTokenRepository
. This is fine as long as the configuredCsrfTokenRepository
is aHttpSessionCsrfTokenRepository
as well, because it accesses the same session attribute.However, if the configured
CsrfTokenRepository
is not aHttpSessionCsrfTokenRepository
, this change affects (and may break) any test that uses the same cachedApplicationContext
, because it now basically uses aHttpSessionCsrfTokenRepository
instead of the configuredCsrfTokenRepository
.TestCsrfTokenRepository
should delegate to the configuredCsrfTokenRepository
to avoid affecting unrelated tests.