From 6b7d215e7e54ebad9337fc72e358790ebb4cd912 Mon Sep 17 00:00:00 2001 From: Chris Hoffman Date: Fri, 29 Jun 2018 09:32:35 -0400 Subject: [PATCH] Clarify performance replication token handling --- website/source/docs/enterprise/replication/index.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/enterprise/replication/index.html.md b/website/source/docs/enterprise/replication/index.html.md index ac64997a1..4069f6884 100644 --- a/website/source/docs/enterprise/replication/index.html.md +++ b/website/source/docs/enterprise/replication/index.html.md @@ -69,7 +69,7 @@ They do not forward service read or write requests until they are elected and be |-------------------------------------------------------------------------------------------------------------------------- |------------------- |-------------------------------------------------------------------------- | | Mirrors the configuration of a primary cluster | Yes | Yes | | Mirrors the configuration of a primary cluster’s backends (i.e.: auth methods, secrets engines, audit devices, etc.) | Yes | Yes | -| Mirrors the tokens and leases for applications and users interacting with the primary cluster | Yes | No. Secondaries use the primary as the source of truth and pass token requests to the primary. When the secondary is promoted, applications must re-auth tokens and obtain new leases from the newly-promoted primary. | +| Mirrors the tokens and leases for applications and users interacting with the primary cluster | Yes | No. Secondaries keep track of their own tokens and leases. When the secondary is promoted, applications must reauthenticate and obtain new leases from the newly-promoted primary. | | Allows the secondary cluster to handle client requests | No | Yes | For more information on the capabilities of performance and disaster recovery replication, see the Vault Replication [API Documentation](/api/system/replication.html).