The Spring Blog
We are pleased to announce the 3.1.0.RC1 release of Spring Cloud Open Service Broker. Support for Open Service Broker API v2.15 is now feature complete, and we expect for this to be the final milestone before a GA release. Thanks to the community for your feedback and contributions! This release includes the following fixes and enhancements:
- Upgrade to Spring Boot 2.2.1.RELEASE
ServiceBrokerInvalidParametersExceptionnow returns an HTTP 400 when a create or update request is malformed or includes invalid parameters. Previously it was, incorrectly, returning an HTTP 422.
AsyncParameterizedServiceInstanceRequestin order to utilize a common request object and reduce redundancy.
- Update reference documentation.
I’m pleased to announce the releases of Spring Security OAuth 2.4.0 and 2.3.8.
For a complete list of changes, please refer to:
|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 am pleased to announce that the Release Candidate 2 (RC2) of the Spring Cloud Hoxton Release Train is available today. The release can be found in Spring Milestone repository. You can check out the Hoxton release notes for more information.
Spring Cloud Hoxton.RC2 is built upon Spring Bot 2.2.1.RELEASE.
Hi, Spring fans! Welcome to another installment of This Week in Spring! I’m in Sydney, Australia, where I’ll begin my tour of Australia, Singapore, Korea, China, and Japan for the Pivotal Summit. I’ll also be doing a Reactive Tour (nested inside the Pivotal Summit Tour) while in China. if you’re in any of the aforementioned countries, or in the Chinese cities of Shenzhen, Hangzhou, Beijing, and Shanghai, then don’t hesitate to say hi! (@starbuxman)
Anyway my friends, we’ve got a lot to get to so let’s get to it!
On behalf of the Spring, Apache Geode, Pivotal GemFire and Pivotal Cloud Cache communities, it is my pleasure to announce the release of Spring Boot for Apache Geode & Pivotal GemFire (SBDG)
1.1.3.RELEASE builds on the new Spring Boot
1.2.1.RELEASE builds on the new Spring Boot
Both versions are available in Maven Central.
See the changelog for full details of the changes in these releases.
On behalf of the community, I’m excited to announce that Spring Vault 2.2 is generally available from repo.spring.io as well as Maven Central. This release ships with several refinements and new features.
The most notable changes are:
Support for PCF-based authentication by using instance identity certificates.
Extensions for a seamless Kotlin 1.3 experience and Kotlin Coroutines support.
WebClientto customize interceptors, filter functions, and default headers.
Vault namespace support (Vault Enterprise edition only).
@VaultPropertySourcesupporting versioned key-value backends.
Added listener and events support to
Support for the Jetty HTTP Client as an alternative reactive HTTP client.
Reactive support for AWS IAM authentication.
On behalf of the team and everyone who has contributed, I’m happy to announce that Spring Boot 2.2.1 has been released and is now available from repo.spring.io and Maven Central.
This release includes 110 fixes, improvements, and dependency upgrades. Thanks to all those who have contributed with issue reports and pull requests.
For those of you upgrading from Spring Boot 2.2.0 to Spring Boot 2.2.1, if you relied on the
@ConfigurationProperties scanning support, please note that this feature is now disabled by default. Scanning of
@ConfigurationProperties needs to be explicitly opted into by adding the
@ConfigurationPropertiesScan annotation. More details related to this change can be found here.