spring-projects / spring-projects/spring-security
Add a WebFlux vs. Servlets Security Section to the docs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Add a section to the Introduction part of the docs about Reactive vs. Servlet security. This section should explain to users what are the fundamental differences between security in a reactive world and a servlet world. topics to touch on in the section are.
- Thread locals variables, how spring security uses them.
- Architecture assumptions spring security made that were no longer true in a reactive world and how did spring security adapt to the reactive requirements
- Background that users should know about how reactive applications execute code, such as schedulers in reactor ... etc.
- Does the reactive security support only apply to project reactor or can it be used with other reactive frameworks like RxJava
- Is there feature parity between reactive and servlet features of spring security, what the things that can't be done in reactive world or a servlet world.
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 in the Introduction portion of the documentation and review existing WebFlux and Servlet security material. Add a section covering thread-local assumptions, reactive execution and schedulers, framework support beyond Reactor, and feature parity; done means each requested topic is clearly explained for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100