From cdd68aff95a96229717559d2cdfb8b4bc72ca294 Mon Sep 17 00:00:00 2001 From: Jeff Mitchell Date: Thu, 13 Jul 2017 19:02:15 -0400 Subject: [PATCH] Reformat some wrapping docs --- .../source/docs/concepts/response-wrapping.html.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/website/source/docs/concepts/response-wrapping.html.md b/website/source/docs/concepts/response-wrapping.html.md index be1e118d61..9e59b2d140 100644 --- a/website/source/docs/concepts/response-wrapping.html.md +++ b/website/source/docs/concepts/response-wrapping.html.md @@ -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.