Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BACKPORT] Manual cherry-pick of failed release/1.14.x backport PRs #26994

Merged
merged 6 commits into from
May 13, 2024
Merged

[BACKPORT] Manual cherry-pick of failed release/1.14.x backport PRs #26994

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
81a0488
[docs] fix lack of space character (#26830)
schavis May 13, 2024
2ff5b7d
Add reading guide for designing Vault clusters (#26947)
schavis May 11, 2024
8fcba06
Remove duplicate nav entry
schavis May 13, 2024
e3a9752
Merge branch 'release/1.14.x' into docs/cherrypick-1.14-batchbackport
schavis May 13, 2024
0297cc8
fix url to anti patterns (#26975)
cjobermaier May 13, 2024
f73ba37
Merge branch 'release/1.14.x' into docs/cherrypick-1.14-batchbackport
schavis May 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/content/docs/enterprise/cluster-design.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ You can help keep your Vault environments healthy by avoiding established
anti-patterns.

The Hashicorp Well-architected framework documentation provides in-depth
[Vault anti-patterns](/well-architected-framework/operational-excellence/operational-excellence-managing-vault-with-terraform) guidance based on
[Vault anti-patterns](/well-architected-framework/operational-excellence/security-vault-anti-patterns) guidance based on
lessons learned by customers operating Vault in the field.

## Step 3: Plan for maintenance at scale
Expand Down
27 changes: 27 additions & 0 deletions website/content/partials/ui/policy-requirements.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
<Warning title="Set UI policies before enabling the UI">

You cannot make policy adjustments or overwrites to the <code>ui/mounts</code>&nbsp;
and <code>ui/resultant-acl</code> endpoints once you enable the Vault UI. Vault
ignores policy updates that target these paths
with <a href="/vault/docs/concepts/policies#deny">explicit <code>deny</code></a> capabilities.

</Warning>

Depending on your Vault configuration, you may need to define UI policies
with different ACL capabilities from the permissions provided by your Vault CLI
policies.

The `default` UI policy includes two paths, **which cannot be modified with
additional policies** once you
[enable](/vault/docs/configuration/ui#activating-the-vault-ui) the UI:

- [/sys/internal/ui/mounts](/vault/api-docs/system/internal-ui-mounts) -
provides a list of currently visible mounts based on the
[`listing_visibility`](/vault/api-docs/system/mounts#listing_visibility)
parameter. `sys/internal/ui/mounts` is an unauthenticated, internal endpoint
used for UI and CLI preflight checks. Requests that include an `X-Vault-Token`
will return all mounts the token has path capabilities on.
- [/sys/internal/ui/resultant-acl](/vault/api-docs/system/internal-ui-resultant-acl) -
repackages authentication information used by the UI. **If you do not have have
permission to call the `ui/resultant-acl` endpoint, you may receive warnings or
errors in the UI**.
Loading