Spring Security committer
Herriman, Utah
On behalf of the community, I’m pleased to announce the release of Spring Security 5.4.5 (release notes). This release delivers bug fixes along with some minor improvements. Users are encouraged to update to the latest patch release.
On behalf of the community, I’m pleased to announce the release of Spring Security 5.4.2 (release notes), 5.3.6 (release notes), and 5.2.8 (release notes). These releases deliver bug fixes along with some minor improvements. Users are encouraged to update to the latest patch release.
With the recent release of Spring Security 5.4, we’d like to announce that maintenance for Spring Security SAML Extensions 1.x will end on 6 October 2021.
SAML 2.0 support has been added to the core Spring Security framework over the last three minor releases. There are two main reasons for this.
First, the extension project is based on a version of OpenSAML that the OpenSAML team no longer supports. This version has known CVEs that make it unsafe for use in a production system.
Second, moving the support to the core Spring Security framework allowed us to simplify the API, use the latest OpenSAML, and add long-requested support for features like multi-tenancy and Spring Boot integration.
On behalf of the community, it is my pleasure to announce the general availability of Spring Security 5.4. This release is the result of the work that went into 5.4.0-M1, 5.4.0-M2, 5.4.0-RC1, and 5.4.0. In combination, they close 250+ tickets.
You can find the highlights of 5.4 in the What’s new section of the Spring Security reference.
As always, we look forward to hearing your feedback!
On behalf of the community, I’m pleased to announce the release of Spring Security 5.4.0-M2! You can find the complete details in the release notes and the highlights below:
On behalf of the community, it is my pleasure to announce the general availability of Spring Security 5.3. This release is the result of the work that went into 5.3.0.M1, 5.3.0.RC1, and 5.3.0.RELEASE. In combination they close 200+ tickets.
You can find the highlights of 5.3 in the What’s new section of the Spring Security reference.
As always, we look forward to hearing your feedback!
|
Note
|
See the latest announcement on Announcing the Spring Authorization Server. This post is a follow-up to Next Generation OAuth 2.0 Support with Spring Security |
In the Spring Security 5.x release train, we’ve endeavored to replace and simplify the feature set found in the Spring Security OAuth 2.x legacy project. In the process, we’ve also added numerous new features, including support for OpenID Connect 1.0.
We are pleased to announce that as of the 5.2 release, we are very close to feature parity with the client and resource server legacy support. What remains is quite minimal, and we fully anticipate announcing feature parity as part of the 5.3 release.
We would like to issue a special thank you to all those in the community who have brought Spring Security this far! We hope to see many more contributions from everyone down the road.
On behalf of the community, I’m pleased to announce the release of Spring Security 5.2.1 (release notes) and 5.1.7 (release notes). These releases deliver bug fixes along with some minor improvements. Users are encouraged to update to the latest patch release.
We have released Spring Security 4.2.13 to address CVE-2019-11272: PlaintextPasswordEncoder authenticates encoded passwords that are null.
Users are encouraged to update immediately.
With Spring Boot, you can override the Spring Security version in Maven like so:
<properties>
<spring-security.version>4.2.13.RELEASE</spring-security.version>
</properties>Or in Gradle like so:
ext['spring-security.version'] = '4.2.13.RELEASE'Note that users of Spring Security 5+ are not affected by this vulnerability.