When upgrading a Spring Boot application from Spring Boot 3.x to 4.x, the library fails because it still relies on the old SecurityAutoConfiguration class from Spring Boot’s security autoconfiguration package.
Specifically, the class:
org.springframework.boot.autoconfigure.security.servlet.SecurityAutoConfiguration
is no longer present / has changed in Spring Boot 4, but the library still refers to it in:
org.zalando.problem.spring.web.autoconfigure.security.ProblemSecurityAutoConfiguration
This makes it impossible to use problem-spring-web with Spring Boot 4 without forking and patching the autoconfiguration.
It would be very helpful if the project could officially support Spring Boot 4 and update the security autoconfiguration accordingly.
When upgrading a Spring Boot application from Spring Boot 3.x to 4.x, the library fails because it still relies on the old SecurityAutoConfiguration class from Spring Boot’s security autoconfiguration package.
Specifically, the class:
is no longer present / has changed in Spring Boot 4, but the library still refers to it in:
This makes it impossible to use problem-spring-web with Spring Boot 4 without forking and patching the autoconfiguration.
It would be very helpful if the project could officially support Spring Boot 4 and update the security autoconfiguration accordingly.