luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

Clarify performance replication token handling

Browse source
This commit is contained in:
Chris Hoffman 2018-06-29 09:32:35 -04:00 committed by GitHub
parent 6f5b8c0e6f
commit 6b7d215e7e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/source/docs/enterprise/replication/index.html.md
View file

@ -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).