Fix autoreplacing issue (#4103)

This commit is contained in:
Viacheslav Vasilyev 2018-03-08 18:01:46 +02:00 committed by Jeff Mitchell
parent f3573c9eea
commit b06c25b552
1 changed files with 5 additions and 5 deletions

View File

@ -1,9 +1,9 @@
---
layout: "guides"
page_title: "Secret as a Service - Guides"
sidebar_current: "guides-secret-mgmt-dataynamic-secrets"
sidebar_current: "guides-secret-mgmt-dynamic-secrets"
description: |-
Vault can dynamically generate secrets on--dataemand for some systems.
Vault can dynamically generate secrets on-demand for some systems.
---
# Secret as a Service: Dynamic Secrets
@ -330,7 +330,7 @@ $ vault token create -policy="apps"
Key Value
--- -----
token e4bdf7dc-cbbf-1bb1-c06c-6a4f9a826cf2
token_accessor 54700b7e--data828-a6c4-6141-96e71e002bd7
token_accessor 54700b7e-d828-a6c4-6141-96e71e002bd7
token_duration 768h0m0s
token_renewable true
token_policies [apps default]
@ -354,7 +354,7 @@ $ vault read database/creds/readonly
Key Value
--- -----
lease_id database/creds/readonly/4b5c6e82--dataf88-0dec-c0cb-f07eee8f0329
lease_id database/creds/readonly/4b5c6e82-df88-0dec-c0cb-f07eee8f0329
lease_duration 1h0m0s
lease_renewable true
password A1a-4urzp0wu92r5s1q0
@ -496,7 +496,7 @@ user name exists.
## Next steps
This guide discussed how to generate credentials on--dataemand so that the access
This guide discussed how to generate credentials on-demand so that the access
credentials no longer need to be written to disk. Next, learn about the
[Tokens and Leases](/guides/identity/lease.html) so that you can control the lifecycle of
those credentials.