mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-11-20 18:21:09 +01:00
Code Issues Projects Releases Wiki Activity

changelog++

Browse Source
This commit is contained in:
Brian Kassouf 2020-02-20 15:09:26 -08:00 committed by GitHub
parent c379a23bea
commit f6ba366940
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -4,13 +4,13 @@ FEATURES:
* **Kerberos Authentication**: We now support Kerberos authentication using a SPNEGO token.
Login can be performed using the Vault CLI, API, or agent.
* **Optional service_registration stanza**: We have introduced a new optional `service_registration` configuration stanza, that allows for service registration to be configured separately from the storage backend. For more, see [#7887](https://github.com/hashicorp/vault/pull/7887/).
* **Kubernetes Service Discovery**: We now support Kubernetes service discovery where, if
configured, Vault will tag Vault pods with their current health status. For more, see [#8249](https://github.com/hashicorp/vault/pull/8249).
* **MongoDB Atlas Secrets**: We now support generating dynamic credentials for both MongoDB Atlas databases
as well as the [Atlas programmatic interface](https://docs.atlas.mongodb.com/tutorial/manage-programmatic-access/).
* **Redshift Database Secrets Engine**: We now support static and dynamic secrets for the Amazon Web Services (AWS) Redshift service.
* **OpenLDAP Secrets Engine**: We now support password management of existing OpenLDAP user entries. For more, see [#8360](https://github.com/hashicorp/vault/pull/8360/).
* **Redshift Database Secrets Engine**: We now support static and dynamic secrets for the Amazon Web Services (AWS) Redshift service.
* **Service Registration Config**: We have introduced a new optional `service_registration` configuration stanza, that allows for service registration to be configured separately from the storage backend. For more, see [#7887](https://github.com/hashicorp/vault/pull/7887/).
IMPROVEMENTS: