spring-projects / spring-projects/spring-security
Strategy for reading the actual CSRF token from the request
Open
Nobody has claimed this yet.
in: web
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Summary
Currently the CsrfTokenRepository allows loading the expected CsrfToken from the request. It would be nice if the actual CSRF token could be a strategy that could be replaced.
Related gh-7537 gh-7538
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading CsrfTokenRepository and the request-handling code that obtains the actual CSRF token. Define the replaceable strategy boundary and verify that the behavior is covered by tests for loading tokens from requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100