From ce7dc22acd6d4508e68f54fbb450f1679abc6f00 Mon Sep 17 00:00:00 2001 From: Nikolaj Volgushev Date: Mon, 7 Aug 2023 14:05:20 +0200 Subject: [PATCH] Present tense --- .../authentication/remote-clusters-privileges.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/x-pack/docs/en/security/authentication/remote-clusters-privileges.asciidoc b/x-pack/docs/en/security/authentication/remote-clusters-privileges.asciidoc index 07f6ee4c4ef37..25adf65442720 100644 --- a/x-pack/docs/en/security/authentication/remote-clusters-privileges.asciidoc +++ b/x-pack/docs/en/security/authentication/remote-clusters-privileges.asciidoc @@ -33,10 +33,10 @@ On the remote cluster that contains the leader index, the {ccr} role requires the `read_ccr` cluster privilege, and `monitor` and `read` privileges on the leader index. -NOTE: If requests will be authenticated with an <>, the API key +NOTE: If requests are authenticated with an <>, the API key requires the above privileges on the **local** cluster, instead of the remote. -NOTE: If requests will be issued <>, +NOTE: If requests are issued <>, then the authenticating user must have the `run_as` privilege on the remote cluster. @@ -136,10 +136,10 @@ local and remote clusters, and then create a user with the required roles. On the remote cluster, the {ccs} role requires the `read` and `read_cross_cluster` privileges for the target indices. -NOTE: If requests will be authenticated with an <>, the API key +NOTE: If requests are authenticated with an <>, the API key requires the above privileges on the **local** cluster, instead of the remote. -NOTE: If requests will be issued <>, +NOTE: If requests are issued <>, then the authenticating user must have the `run_as` privilege on the remote cluster.