spring-projects / spring-projects/spring-security
Provide access to default configuration for ServerHttpSecurity
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
WebFluxSecurityConfiguration.springSecurityFilterChain(ServerHttpSecurity http) initializes ServerHttpSecurity with a default configuration. The access is currently private. We should provide a means to allow access (likely indirectly) for users to initialize using the standard default configuration for ServerHttpSecurity and than they can customize the configuration to meet their requirements.
One implementation idea is to allow custom configurations to consume the default ServerHttpSecurity via a Consumer<ServerHttpSecurity>.
ReactiveManagementWebSecurityAutoConfiguration may be a good candidate as a Consumer<ServerHttpSecurity> instead of it directly building a SecurityWebFilterChain via it's own instance of ServerHttpSecurity.
Related #6314
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 WebFluxSecurityConfiguration.springSecurityFilterChain(ServerHttpSecurity http) and ReactiveManagementWebSecurityAutoConfiguration, then review related issue #6314. Determine how custom configurations can consume the standard default ServerHttpSecurity without creating a separate instance. Done means users can access that default configuration and customize it for their requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100