spring-projects / spring-projects/spring-security
Consider merging `AuthenticationManager` and `AuthenticationProvider`
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
We should consider merging AuthenticationManager and AuthenticationProvider into a single interface, since both APIs are almost identical.
We should also consider introducing a more generalized API, for example, Authenticator, and discontinue usage of AuthenticationManager and AuthenticationProvider.
Related gh-13266, gh-11428
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 comparing the AuthenticationManager and AuthenticationProvider APIs and reviewing related issues gh-13266 and gh-11428. Determine whether a single or generalized Authenticator API is agreed upon, and define what retiring the existing APIs would require before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100