spring-projects / spring-projects/spring-security
SEC-2886: Session flag to bypass CSRF
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Christopher Smith (Migrated from SEC-2886) said:
My application uses identical URI endpoints for both Web and non-Web clients. While I appreciate the importance of CSRF protection for Web interfaces, it would be helpful to be able to specifically tag a session as "this is from a non-Web client and should be ignored by CsrfFilter", probably with a specifically-named attribute. This would provide a straightforward and comprehensible point for implementing per-client CSRF policy.
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 the CsrfFilter entry point and the surrounding CSRF configuration to understand where a session-level policy could be represented. Define the expected behavior for tagged non-Web sessions, including how the existing CSRF protection remains unchanged for other clients, and verify the behavior with focused tests.
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
- 32/100