Rewrite WebSecurityConfig to use the lambda DSL. #134
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spring Security has two forms of DSLs for configuring the HttpSecurity object, one based on method chaining and one based on lambdas. 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.
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