Rob Winch is employed by VMware as the project lead of security related projects within Spring. He is also a committer on the core Spring Framework and co-author for Spring Security LiveLessons and a Spring Security book. In the past he has worked in the health care industry, bioinformatics research, high performance computing, and as a web consultant. When he is not sitting in front of a computer he enjoys cycling with his friends.
On behalf of the team and everyone who has contributed, I am pleased to announce the availability of Spring Security 7.0.0-RC1, 6.4.12 and 6.5.6.
The highlights of 7.0.0-RC1 include:
For a complete list of changes, refer to the changelogs:
It gives me great pleasure to announce that the Spring Session Hazelcast project will now be led by the Hazelcast Team.
NOTE: This announcement is in alignment with our announcement Spring Session MongoDB: Now Led by MongoDB Team.
For ten years Spring Session has provided the infrastructure for transparently replacing session stores in a vendor independent manner. With that infrastructure in place, it is just a matter of implementing SessionRepository javadoc in order to support storing session information in a new datastore.
I cannot think of a team who has more Hazelcast experience than the Hazelcast team themselves and so it gives me great pleasure to announce the Hazelcast team will be leading the next generation of Spring Session Hazelcast! To best enable this transition, the next generation of releases will be in a new GitHub repository and have new Maven coordinates. Support for existing generations of Spring Session Hazelcast will continue to be maintained by the Spring Session team as described by the Spring Support Policy…
It gives me great pleasure to announce that the Spring Session MongoDB project will now be led by the MongoDB Team.
NOTE: This announcement is in alignment with our announcement Spring Session Hazelcast: Now Led by Hazelcast Team.
For ten years Spring Session has provided the infrastructure for transparently replacing session stores in a vendor independent manner. With that infrastructure in place, it is just a matter of implementing SessionRepository javadoc in order to support storing session information in a new datastore.
I cannot think of a team who has more MongoDB experience than the MongoDB team themselves and so it gives me great pleasure to announce that the MongoDB team will be leading the next generation of Spring Session MongoDB! To best enable this transition, the next generation of code will be hosted in a new GitHub repository and have new Maven coordinates, both available in November. Support for existing generations of Spring Session MongoDB will continue to be maintained by the Spring Session team as described by the Spring Support Policy…
On behalf of the team and everyone who has contributed, I am pleased to announce the general availability of Spring Session 3.5.0!
This release contains fixes, dependency updates, and enhancements to position the project for Spring Session 4.0.0 this fall.
On behalf of the team and everyone who has contributed, I am pleased to announce the availability of Spring Security 6.3.9.
Please check the changelog for more details.
On behalf of the team and everyone who has contributed, I am pleased to announce the availability of Spring Security 6.4.5.
Please check the changelog for more details.
The Spring team will be rolling out a simplified contribution process that replaces the requirement to sign a Contributor License Agreement (CLA) with a Developer Certificate of Origin (DCO). The process will start this week with Spring Framework, Spring Security, & Spring Boot and then roll out to the entire Spring portfolio.
Spring has long used a permissive Contributor License Agreement (CLA) in order to provide legal protections to the Spring project, users, and the Spring team. Long time contributors may remember that signing the CLA originally involved emailing a signed PDF of…
On behalf of the Spring Security team and everyone who contributed to this release, I am delighted to announce the general availability of Spring Security Kerberos 2.1.0!
This release brings in bug fixes, version updates, and lots of compatability fixes.
On behalf of the team and everyone who has contributed, I am pleased to announce that the Spring Security 5.8.7, 6.0.7, 6.1.4, and 6.2.0-M1 are available now which fix CVE-2023-34042.
Please refer to the releases page for more detail on what is included in each release.
On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Security 6.1.1, 6.0.4, 5.8.4, 5.7.9, and 5.6.11 are available now. The releases are mostly composed of bug fixes, dependency upgrades, and documentation improvements.
To learn more, please visit the 6.1.1, 6.0.4, 5.8.4, 5.7.9, and 5.6.11 release summaries.
VMware offers training and certification to turbo-charge your progress.
Learn moreTanzu Spring offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.
Learn moreCheck out all the upcoming events in the Spring community.
View all