Spring Vault 3.0 is officially GA.

Spring Vault provides client-side support for accessing, storing, and discarding confidential data, as well as familiar Spring abstractions for developers. It provides low-level and high-level abstractions for interacting with Vault, freeing developers from worrying about infrastructure issues.

Based on HashiCorp’s Vault, developers can manage external confidential data of applications in all environments in one central location. Spring Vault can manage static and dynamic confidential data, such as application data, usernames/passwords for remote applications/resources, and provide credentials for external services (such as MySQL, PostgreSQL, Apache Cassandra, Consul, AWS, etc.).

Important changes in Spring Vault 3.0:

• Based on Java 17 with support for Java 19

Spring Vault 3.0 uses Java 17 as the minimum supported version. If developers are currently using Java 8 or Java 11, they need to upgrade the JDK before developing Spring Vault 3.0 applications.

• Support for additional HTTP clients, including the reactive JDK HTTP client

With the upgrade of Spring, Spring Vault’s support for Apache HTTP Client has also been upgraded to version 5, while supporting the reactive use of asynchronous Apache HTTP 5 clients.

• Support for Vault repositories with a versioned Key/Value secret engine

Vault repositories can now store and retrieve their secrets in the versioned Key/Value secrets engine (k/v version 2). See the documentation for details.

Spring Vault 3.0 is based on and requires Spring Framework 6.

Other Spring projects that have been upgraded for this release include:

• Spring Data 2022.0.0
• Spring Security 6.0.0

Many third-party dependencies have also been updated, notable ones include:

• Reactor 2022.0.0

• Apache HTTP Client 5.1

• AWS SDK 2.18.24

• Jackson 2.14.1

• Jetty Reactive Client 3.0.7

• Netty 4.1.85

• Kotlin 1.7.21

• Google Cloud IAMcredential 2.6.0

• Google OAuth2 Auth Library 1.13.0

Release Notes | Release Notes