Hear from the Spring team this January at SpringOne. >

Rob Winch

Rob Winch

Spring Security, Session, & LDAP project lead

Rob Winch is employed by Pivotal as the project lead of security related projects within Spring. He is also a committer on the core Spring Framework and co-author of the Spring Security 3.1 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 playing the guitar.
Blog Posts by Rob Winch

Spring Session 3.0.0-RC1

Spring Session 3.1.0-RC1 has been released. The biggest news from this release is that Spring Session Geode was removed which means all of the Spring Modules now belong to the same lifecycle. This means that the Spring Session BOM no longer uses CalVer and instead uses the same version as the remaining Spring Session modules. For example, in this release the version of spring-session-bom is 3.0.0-RC1.

You can view the release notes for additional details around this release.


Spring Session 2022.0.0-M3 Released

On behalf of the team, I’m pleased to announce the release of Spring Session 2022.0.0-M3. These releases deliver, enhancements, bug fixes, and dependency upgrades.
For your convenience, Spring Boot will pick up these artifacts with its upcoming releases.

The following modules were updated as part of 2022.0.0-M3:


Spring Security 5.5.0-RC2 released

On behalf of the community, I’m pleased to announce the release of Spring Security 5.5.0-RC2!

After releasing 5.5.0-RC1 we received some feedback on our APIs that required further refinements. This release finalizes the APIs for the 5.5.0 release later this month.

You can find the complete details in the release notes.


Spring Security 5.4.4, 5.3.8, and 5.2.9 released

On behalf of the community, I’m pleased to announce the release of Spring Security 5.4.4 (release notes), 5.3.8 (release notes), and 5.2.9 (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 an issue releasing 5.4.3 and 5.3.7 which caused us to need to release 5.4.4 and 5.3.8.