On behalf of the community, I am pleased to announce the first milestone releases of Spring Vault and Spring Cloud Vault 1.0.0.M1.

The artifacts are available in the Milestone repo.

What is Spring Vault and Spring Cloud Vault?

Spring Vault is a client for HashiCorp Vault that provides familiar Spring abstractions. It comes with @VaultPropertySource that exposes encrypted properties from Vault the Environment and VaultTemplate to access secrets stored and encrypted inside Vault.

@Configuration
@VaultPropertySource("secret/my-application")
public class AppConfig extends…

In my previous post about Managing Secrets with Vault, I introduced you to Vault and how to store arbitrary secrets using the generic secret backend. Vault can manage more than just secret data like API keys, passwords, and other sensitive string-like data. Today we’re taking a look at Vault’s integration with databases, services, and certificates.

Database credentials tend to be static

When it comes to databases, the regular workflow of getting credentials applying for a database is asking some operator or a self-service tool to give you credentials so your application can log into the…

On behalf of the Spring Data team, I’m happy to announce the first milestone of the Ingalls release train. The release ships 230 tickets fixed! The most noteworthy new features are:

• Use of method handles for property access in conversion subsystem (Commons, MongoDB).
• Upgrade to Cassandra 3.0 for Spring Data Cassandra (see the updated examples for details).
• Support for declarative query methods for Cassandra repositories.
• Support for Redis geo commands.
• Any-match mode for query-by-example.
• Support for XML and JSON based projections for REST payloads (see the example for details)

Find a curated change log in our release train wiki or skim through a full list of changes in JIRA…

Passwords, API keys and confidential data fall into the category of secrets. Storing secrets the secure way is a challenge with limiting access and a true secure storage. Let's take a look at Hashicorp Vault and how you can use it to store and access secrets.

How do you store Secrets?

Passwords, API keys, secure Tokens, and confidential data fall into the category of secrets. That's data which shouldn't lie around. It mustn't be available in plaintext in easy to guess locations. In fact, it must not be stored in plaintext in any location.

Sensitive data can be encrypted by using the Spring Cloud Config Server or TomEE. Encrypted data is one step better than unencrypted. Encryption imposes on the other side the need for decryption on the user side which requires a decryption key to be distributed. Now, where do you put the key? Is the key protected by a passphrase? Where do you put the passphrase? On how many systems do you distribute…

On behalf of the Spring Data team I’d like to announce the availability of the second service release of the Spring Data Hopper release train. The release ships 103 issues fixed. We fixed a couple of bugs in the area of repository projections, especially for JPA users and introduce Hibernate 5.2 compatibility with this release (also already back-ported to the Gosling release train for inclusion in the upcoming service release). Hopper SR2 is a recommended upgrade for all Hopper users and also users of previous release trains.

Here are the released modules:

• Spring Data Cassandra 1.4.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Commons 1.12.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Couchbase 2.1.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Elasticsearch 2.0.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data Envers 1.0.2 - Artifacts - JavaDocs - Documentation
• Spring Data Gemfire 1.8.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data JPA 1.10.2 - Artifacts - JavaDocs - Documentation - Changelog
• Spring Data KeyValue 1.1.2 - Artifacts - JavaDocs - Documentation - …