spring-projects / spring-projects/spring-security

Add remaining lambda methods to configuration

Open
#13,003 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

  • WebSecurity#ignoring
  • LdapAuthenticationProviderConfigurer#passwordCompare
  • AuthenticationManagerBuilder#ldapAuthentication
  • AuthenticationManagerBuilder#inMemoryAuthentication
  • AuthenticationManagerBuilder#jdbcAuthentication
  • AuthenticationManagerBuilder#userDetailsService

The non-lambda methods should be deprecated

Related to:

  • #12629

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

Review the six listed methods and the related issue #12629 to understand the remaining lambda configuration scope. Track each checklist item through its existing configuration API, then verify that every lambda method is covered and each non-lambda method is deprecated.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
backend, security
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.