You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spring Security has two forms of DSLs for configuring the HttpSecurity
object, one based on method chaining and [one based on lambdas][lambda-dsl].
The latter is generally more readable, as it makes it clear the scope of each
configuration block. In fact the method chaining syntax is deprecated in Spring
Security 6.2, and [will be removed in 7.0][migration].
We were using an inconsistent mix of the two. This cleans it up and uses
the lambda DSL throughout. The only exception to this is the
`AuthenticationManager` configuration, which [for some reason doesn't
have a lambda DSL][sec13003]
[lambda-dsl]: https://spring.io/blog/2019/11/21/spring-security-lambda-dsl
[migration]: https://docs.spring.io/spring-security/reference/migration-7/configuration.html
[sec13003]: spring-projects/spring-security#13003
Uh oh!
There was an error while loading. Please reload this page.
WebSecurity#ignoring
LdapAuthenticationProviderConfigurer#passwordCompare
AuthenticationManagerBuilder#ldapAuthentication
AuthenticationManagerBuilder#inMemoryAuthentication
AuthenticationManagerBuilder#jdbcAuthentication
AuthenticationManagerBuilder#userDetailsService
The non-lambda methods should be deprecated
Related to:
The text was updated successfully, but these errors were encountered: