-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[boot-upgrade] [Spring-Security] Removed WebSecurityConfigurerAdapter #979
Labels
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: refactoring
type: enhancement
Milestone
Comments
martinlippert
added
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: refactoring
and removed
status: waiting-for-triage
labels
Feb 24, 2023
Marker and quickfix added to IDE: 7c5dee4 |
Done for 4.18.0 release.
|
So we can close this one and open new and separate issues for the work to be continued in the 4.18.1 cycle? (@BoykoAlex ) |
Remaining bits moved to #1001 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
for: eclipse
something that is specific for Eclipse
for: vscode
something that is specific for VSCode
theme: refactoring
type: enhancement
The
WebSecurityConfigurerAdapter
is deprecated in the last versions of Spring-Security 5.x used in Spring-Boot 2.7.x. As of Spring-Security 6.x and Spring-Boot 3.x theWebSecurityConfigurerAdapter
is removed.Migration guide for the Removed
WebSecurityConfigurerAdapter
The migration guide splits migration in 5 cases (parts are completed in
WebSecurityConfigurerAdapter
recipe in rewrite-spring project:Remaining cases are LDAP and JDBC authentication which seem challenging as methods bodies requires significant changes even going outside the scope of one method. Looks like only some migration cases are possible to cover with rewrite. It is challenging to write code that would reliably determine conditions when it is possible to perform automated migration.
The text was updated successfully, but these errors were encountered: