From ed52771d63e28f110b03c4ec9da8085fb65cba38 Mon Sep 17 00:00:00 2001 From: Nick Cabatoff Date: Wed, 29 Jun 2022 12:28:49 -0400 Subject: [PATCH] Rewrite a confusing bit of policies docs re parameter constraints. (#16182) --- website/content/docs/concepts/policies.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/website/content/docs/concepts/policies.mdx b/website/content/docs/concepts/policies.mdx index 56b25e89c5..771f22f074 100644 --- a/website/content/docs/concepts/policies.mdx +++ b/website/content/docs/concepts/policies.mdx @@ -340,10 +340,8 @@ path take precedence over permissions on parameters. See the [API Specification](/api-docs/secret/kv/kv-v2) for more information. -In Vault, data is represented as `key=value` pairs. Vault policies can -optionally further restrict paths based on the keys and data at those keys when -evaluating the permissions for a path. The optional finer-grained control -options are: +Policies can take into account HTTP request parameters to further +constrain requests, using the following options: - `required_parameters` - A list of parameters that must be specified.