mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-05 13:08:07 +00:00
adding explanation for allow_store_key flag , based on internal engineering conversation. (#17258)
This commit is contained in:
@@ -87,8 +87,8 @@ $ curl \
|
|||||||
a key into the configured backend even if a key is present, if set to false those operations are forbidden
|
a key into the configured backend even if a key is present, if set to false those operations are forbidden
|
||||||
if a key exists.
|
if a key exists.
|
||||||
|
|
||||||
- `allow_store_key` `(string: "false")` - Controls the ability for Vault to import a key
|
- `allow_store_key` `(string: "false")` - Controls the ability for Vault to export a Vault private key
|
||||||
to the configured backend, if "false" those operations will be forbidden.
|
to the configured HSM, if "false" those operations will be forbidden.
|
||||||
|
|
||||||
- `any_mount` `(string: "false")` - Allow usage from any mount point within the namespace if "true". If "false"
|
- `any_mount` `(string: "false")` - Allow usage from any mount point within the namespace if "true". If "false"
|
||||||
specific mount points will need their `allowed_managed_keys` parameter to be updated with the key name to
|
specific mount points will need their `allowed_managed_keys` parameter to be updated with the key name to
|
||||||
|
|||||||
Reference in New Issue
Block a user