upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-09 08:55:13 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Reformat some wrapping docs

Browse source
This commit is contained in:
Jeff Mitchell 2017-07-13 19:02:15 -04:00
parent 203807aea7
commit cdd68aff95
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
website/source/docs/concepts/response-wrapping.html.md
View file

@ -52,8 +52,10 @@ eventual certificate remains private. The end service can be assured that only
it will see the generated private key and that any malfeasance is detected.
This can significantly reduce the complexity of any relaying third party.
One final note: if the wrapped response is an authentication response
containing a Vault token, the token's accessor will be made available in the
returned wrap information. This allows privileged callers to generate tokens
for clients and revoke these tokens (and their created leases) at an
appropriate time, while never being exposed to the actual generated token IDs.
## Wrapping Tokens
If the wrapped response is an authentication response containing a Vault token,
the token's accessor will be made available in the returned wrap information.
This allows privileged callers to generate tokens for clients and revoke these
tokens (and their created leases) at an appropriate time, while never being
exposed to the actual generated token IDs.