luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Update upgrade guide with HSM info

This commit is contained in:
Jeff Mitchell 2017-11-16 11:04:46 -05:00
parent 00dfc1c4de
commit 422c1898c8
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -2,6 +2,10 @@
DEPRECATIONS/CHANGES:
* HSM config parameter requirements: When using Vault with an HSM, a new
paramter is required: `hmac_key_label`. This performs a similar function to
`key_label` but for the HMAC key Vault will use. Vault will generate a
suitable key if this value is specified and `generate_key` is set true.
* API HTTP client behavior: When calling `NewClient` the API no longer
modifies the provided client/transport. In particular this means it will no
longer enable redirection limiting and HTTP/2 support on custom clients. It

9
website/source/guides/upgrading/upgrade-to-0.9.0.html.md
View File

@ -71,6 +71,14 @@ for the encryption keyring itself.
To better reflect its actual use, the `generic` backend is now `kv`. Using
`generic` will still work for backwards compatibility.
### HSM Users Need to Specify New Config Options (In 0.9)
When using Vault with an HSM, a new paramter is required: `hmac_key_label`.
This performs a similar function to `key_label` but for the HMAC key Vault will
use. Vault will generate a suitable key if this value is specified and
`generate_key` is set true. See [the seal configuration page][pkcs11-seal] for
more information.
### API HTTP client behavior (In 0.9)
When calling `NewClient` the API no longer modifies the provided
@ -111,3 +119,4 @@ Audit request and response entires are still in RFC3339 format but now have a
granularity of nanoseconds.
[generate-root]: https://www.vaultproject.io/api/secret/pki/index.html#generate-root
[pkcs11-seal]: https://www.vaultproject.io/docs/configuration/seal/pkcs11.html