EB-6: Update Security configuration for Spring Security 6.4 compatibility #21
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.
Overview
This PR addresses EB-6: Review and update Security configuration for Spring Security 6.4 by removing deprecated API usage in
SecurityConfig.javato ensure compatibility with Spring Security 6.4.11.Changes Made
Removed Deprecated Authentication Configuration
configureGlobal(AuthenticationManagerBuilder auth)method (lines 55-59)UserDetailsServicebean registration following Spring Security 6.x best practicesUpdated Imports
org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder(no longer needed)org.springframework.security.core.userdetails.UserDetailsService(required for the new bean)Technical Details
Before (Deprecated Pattern):
After (Spring Security 6.x Pattern):
Verification
✅ Code compiles successfully with
mvn clean compile -DskipTests✅ No compilation warnings or errors
✅ All Spring Security APIs used are non-deprecated in Spring Security 6.4.x
✅ Existing authentication behavior preserved (users authenticate through
AccountService.loadUserByUsername()with BCrypt)Scope
This PR is focused on compatibility only, not security improvements. The following items are intentionally out of scope for this ticket:
UserDetailsimplementation inAccount.javaRelated Work
Link to Devin run
https://app.devin.ai/sessions/74f196092a3f43329a856f3abeb6cd27
Requested by
Alex Peng (alex.peng@windsurf.com) - @alexjpeng