{"action":"closed","issue":{"url":"https://api.github.com/repos/hashicorp/vault/issues/4815","repository_url":"https://api.github.com/repos/hashicorp/vault","labels_url":"https://api.github.com/repos/hashicorp/vault/issues/4815/labels{/name}","comments_url":"https://api.github.com/repos/hashicorp/vault/issues/4815/comments","events_url":"https://api.github.com/repos/hashicorp/vault/issues/4815/events","html_url":"https://github.com/hashicorp/vault/issues/4815","id":334642171,"node_id":"MDU6SXNzdWUzMzQ2NDIxNzE=","number":4815,"title":"Contradicting statements in replication guide regarding tokens","user":{"login":"raoofm","id":12846989,"node_id":"MDQ6VXNlcjEyODQ2OTg5","avatar_url":"https://avatars2.githubusercontent.com/u/12846989?v=4","gravatar_id":"","url":"https://api.github.com/users/raoofm","html_url":"https://github.com/raoofm","followers_url":"https://api.github.com/users/raoofm/followers","following_url":"https://api.github.com/users/raoofm/following{/other_user}","gists_url":"https://api.github.com/users/raoofm/gists{/gist_id}","starred_url":"https://api.github.com/users/raoofm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raoofm/subscriptions","organizations_url":"https://api.github.com/users/raoofm/orgs","repos_url":"https://api.github.com/users/raoofm/repos","events_url":"https://api.github.com/users/raoofm/events{/privacy}","received_events_url":"https://api.github.com/users/raoofm/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-06-21T20:19:06Z","updated_at":"2018-06-29T13:33:02Z","closed_at":"2018-06-29T13:33:02Z","author_association":"NONE","body":"[Here](https://www.vaultproject.io/docs/enterprise/replication/index.html) it mentions that\r\n> In performance replication, secondaries keep track of their own tokens and leases but share the underlying configuration, policies, and supporting secrets (K/V values, encryption keys for transit, etc).\r\n\r\nBut below it in the capabilities comparison table between DR and Perf on the same page it mentions\r\n> Mirrors the tokens and leases for applications and users interacting with the primary cluster\r\nDR - Yes\r\nPerf - 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.\r\n\r\n"}}
{"actor":{"display_login":"chrishoffman"}}