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

Backport of Add note about vault kv get to Proxy docs into release/1.18.x #28421

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Backport of Add note about vault kv get to Proxy docs into release/1.18.x #28421

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions website/content/docs/agent-and-proxy/proxy/caching/static-secret-caching.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,16 @@ request to Vault but caches the response before forwarding it to the client. If
that client makes subsequent `GET` requests for the same secret, Vault Proxy
serves the cached response rather than forwarding the request to Vault.

<Tip title="'Offline' Secret Access and CLI KV Get">

Vault Proxy does not cache any non-KV API responses. While KV secrets can be retrieved even if
Vault is unavailable, other requests cannot be served. As a result, using the `vault kv`
CLI command, which sends a request to `/sys/internal/ui/mounts` before the KV `GET` request,
will require a real request to Vault and cannot be served entirely from the cache or
when Vault is unavailable (you can use `vault read` instead).

</Tip>

Similarly, when a token requests access to a KV secret, it must complete a
success `GET` request. If the request is successful, Proxy caches the fact that
the token was successful in addition to the result. Subsequent requests by the
Expand Down
Loading