spring-projects / spring-projects/spring-security

SEC-2998: Make it possible for AuthenticationManagerBuilder to expose its UserDetailsService in Spring Boot

Open
#3,209 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

in: config type: enhancement type: jira
Dominant language
Java
Stars
9.6k
Forks
6.3k
Avg merge
2d 11h
Merged PRs (30d)
52

Description

Dave Syer (Migrated from SEC-2998) said:

Spring Boot has a hack to expose the UserDetailsService in its default AuthenticationManager. The hack can be reverted if an alternative API can be provided in Spring Security so that the "defaultUserDetailsService" in the AuthenticationManagerBuilder is more accessible, either directly or indirectly when calling AuthenticationManagerBuilder.apply(). Details of the hack can be found in the attached github issue (and a failing test case without the hack).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with AuthenticationManagerBuilder and its defaultUserDetailsService, then review how AuthenticationManagerBuilder.apply() is used by Spring Boot's current workaround. The work is complete when Spring Security exposes a supported alternative API and the Spring Boot hack can be removed, with the referenced failing test case passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
authentication, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.