For complete details on migrating from Spring Security 3 to Spring Security 4 refer to one of the guides below:
* http://docs.spring.io/spring-security/site/migrate/current/3-to-4/html5/migrate-3-to-4-xml.html[Migrating from Spring Security 3.x to 4.x (XML Configuration)]
* http://docs.spring.io/spring-security/site/migrate/current/3-to-4/html5/migrate-3-to-4-jc.html[Migrating from Spring Security 3.x to 4.x (Java Configuration)]
* https://jira.spring.io/browse/SEC-2790[Deprecate @EnableWebMvcSecurity] - by updating the minimum Spring Version, we can now allow defaulting MVC integration with `@EnableWebSecurity` but still allow it to be overridden
[[m3to4]]
=== Migrating from 3.x to 4.x
As exploits against applications evolve, so must Spring Security.
As a major release version, the Spring Security team took the opportunity to make some non-passive changes which focus on:
* Ensuring Spring Security is more https://www.owasp.org/index.php/Establish_secure_defaults[secure by default]
For complete details on migrating from Spring Security 3 to Spring Security 4 refer to one of the guides below:
* http://docs.spring.io/spring-security/site/migrate/current/3-to-4/html5/migrate-3-to-4-xml.html[Migrating from Spring Security 3.x to 4.x (XML Configuration)]
* http://docs.spring.io/spring-security/site/migrate/current/3-to-4/html5/migrate-3-to-4-jc.html[Migrating from Spring Security 3.x to 4.x (Java Configuration)]
[[jc]]
== Java Configuration
@ -9486,4 +9410,6 @@ Provides Spring Security's JSP tag implementations.
@@ -9486,4 +9410,6 @@ Provides Spring Security's JSP tag implementations.
| Required if you are using SPEL expressions in your tag access constraints.