Spring Cloud Vault Config now supports property-based SSL configuration using spring.cloud.vault.ssl.* properties to enable server certificate validation.
Introducing a Vault-specific configuration requires to configure HTTP clients individually and so this change adds configuration support for Apache HTTP Components, Netty and the OkHttp client. Clients are picked configured if they exist on the class path.
Fixes gh-7
Relocate tests using Vault as config source to config client. Move integration tests to parent package as all tests are integration tests. Enhance JavaDoc. Order travis.yml file according the execution sequence.
We now support credential generation for MySQL, PostgreSQL and Apache Cassandra databases.
Credential generation can be turned on using properties and stores username/password in properties according to Spring Boot's auto configuration.
Fixes gh-2.
Support app-id authentication using app id and user id. User-ids are generated either from the SHA-256 hex-encoded IP address or using the Mac address represented as hex without separators. Network addresses are obtained from the InetAddress.getLocalHost() method.
Tests use a test @Rule VaultRule to ensure Vault is unsealed and provides a persistent token that can be used as root token during tests. The token is static so it can be reused across multiple test runs without restarting vault. Add tests for generic secret backend usage with a static token and app-id authentication. Add tests for app-id authentication using IP address and Mac-address user-ids.
