spring-projects / spring-projects/spring-security
HttpSecurity authentication configurers should use AuthenticationFilter
Open
Nobody has claimed this yet.
status: waiting-for-triage
type: enhancement
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
One way to opt-in to this behavior may be when an application chooses to wire an AuthenticationManager directly in the configurer.
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 tracing HttpSecurity authentication configurers and how they currently obtain or wire an AuthenticationManager, then compare that path with AuthenticationFilter. The issue suggests opt-in behavior when an application wires an AuthenticationManager directly, but does not name files or tests. Done would require a settled design and corresponding coverage for the intended configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100