On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Security 5.8.0-M2 is available now.
This release includes dependency upgrades, bug fixes, and enhancements. Here are a few noteworthy changes:
See the 5.8.0-M2 release notes for more details.
A new round of releases for Spring Security is available now. The new releases fix a bug where the StrictHttpFirewall incorrectly rejects valid CJKV characters.
Please take a look at the release notes for more information.
On behalf of the community, I’m pleased to announce the release of Spring Security 5.7.0-RC1!
In addition to dependency upgrades, bug fixes, and minor enhancements, the release candidate contains a few noteworthy changes:
Introduced SecurityContextHolderFilter - Ability to require explicit saving of the SecurityContext
Added DSL support for Cross Origin Policies headers
Allow configuring PKCE for confidential clients
Added SAML 2.0 Login & Single Logout XML support
This release candidate is a good opportunity to give feedback before the actual GA release in mid-May. We look forward to hearing from you.
On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Security 5.6.3 and 5.5.6 are available now.
On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Security 6.0.0-M1 and 5.7.0-M1 are available now.
This initial 6.0 milestone covers the baseline upgrade efforts, in particular requiring JDK 17+ and migrating to the Jakarta EE 9 APIs, required by Spring Framework 6, as announced in this blog post.
For the release changes, please refer to the releases page.
Stay tuned for the announcement of Spring Boot 3.0.0-M1 this week!
On behalf of the community, I’m pleased to announce the release of Spring Security 5.2.15 (release notes), Spring Security 5.3.13 (release notes), Spring Security 5.4.10 (release notes), Spring Security 5.5.4 (release notes) and Spring Security 5.6.1 (release notes). These releases deliver bug fixes along with some minor improvements. Users are encouraged to update to the latest patch release.
NOTE: There was a missing dependency update in 5.2.14.RELEASE which caused us to need to release 5.2.15.RELEASE.
