You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/10/14 06:21:50 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#97035ba)
This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 44aa08d9ca6 Docs sync done from apache/pulsar(#97035ba)
44aa08d9ca6 is described below
commit 44aa08d9ca6853e65c9dc6e094f18ecc66ecfbb6
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Fri Oct 14 06:21:45 2022 +0000
Docs sync done from apache/pulsar(#97035ba)
---
site2/website-next/docs/security-overview.md | 8 ++++----
.../versioned_docs/version-2.1.0-incubating/security-overview.md | 2 +-
.../versioned_docs/version-2.1.1-incubating/security-overview.md | 2 +-
.../versioned_docs/version-2.10.0-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.10.1-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.10.x/security-overview.md | 2 +-
.../versioned_docs/version-2.2.0/security-overview.md | 2 +-
.../versioned_docs/version-2.2.1/security-overview.md | 2 +-
.../versioned_docs/version-2.3.0/security-overview.md | 2 +-
.../versioned_docs/version-2.3.1/security-overview.md | 2 +-
.../versioned_docs/version-2.3.2/security-overview.md | 2 +-
.../versioned_docs/version-2.5.0/security-overview.md | 2 +-
.../versioned_docs/version-2.5.1/security-overview.md | 2 +-
.../versioned_docs/version-2.5.2/security-overview.md | 2 +-
.../versioned_docs/version-2.6.0/security-overview.md | 2 +-
.../versioned_docs/version-2.6.1/security-overview.md | 2 +-
.../versioned_docs/version-2.6.2/security-overview.md | 2 +-
.../versioned_docs/version-2.6.3/security-overview.md | 2 +-
.../versioned_docs/version-2.6.4/security-overview.md | 2 +-
.../versioned_docs/version-2.7.0/security-overview.md | 2 +-
.../versioned_docs/version-2.7.1/security-overview.md | 2 +-
.../versioned_docs/version-2.7.2/security-overview.md | 2 +-
.../versioned_docs/version-2.7.3/security-overview.md | 2 +-
.../versioned_docs/version-2.7.4/security-overview.md | 2 +-
.../versioned_docs/version-2.7.5/security-overview.md | 2 +-
.../versioned_docs/version-2.8.0-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.8.1-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.8.2-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.8.3-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.8.x/security-overview.md | 2 +-
.../versioned_docs/version-2.9.0-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.9.1-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.9.2-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.9.3-deprecated/security-overview.md | 2 +-
.../versioned_docs/version-2.9.x/security-overview.md | 2 +-
35 files changed, 38 insertions(+), 38 deletions(-)
diff --git a/site2/website-next/docs/security-overview.md b/site2/website-next/docs/security-overview.md
index 3e9a90874bd..3008e065f98 100644
--- a/site2/website-next/docs/security-overview.md
+++ b/site2/website-next/docs/security-overview.md
@@ -7,13 +7,13 @@ sidebar_label: "Overview"
As the central message bus for a business, Apache Pulsar is frequently used for storing mission-critical data. Therefore, enabling security features in Pulsar is crucial. This chapter describes the main security controls that Pulsar uses to help protect your data.
Pulsar security is based on the following core pillars.
-* [Encryption](#encryption)
-* [Authentication](#authentication)
-* [Authorization](#authorization)
+- [Encryption](#encryption)
+- [Authentication](#authentication)
+- [Authorization](#authorization)
By default, Pulsar configures no encryption, authentication, or authorization. Any clients can communicate to Pulsar via plain text service URLs. So you must ensure that Pulsar accessing via these plain text service URLs is restricted to trusted clients only. In such cases, you can use network segmentation and/or authorization ACLs to restrict access to trusted IPs. If you use neither, the state of the cluster is wide open and anyone can access the cluster.
-Apache Pulsar uses an [Authentication Provider](#authentication) or an [Authentication Provider Chain](security-extending.md/#proxybroker-authentication-plugin) to establish the identity of a client and then assign a *role token* (a string like `admin` or `app1`)to that client. This role token can represent a single client or multiple clients and is then used for [Authorization](security-authorization.md) to determine what the client is authorized to do. You can use roles to control perm [...]
+Apache Pulsar uses an [Authentication Provider](#authentication) or an [Authentication Provider Chain](security-extending.md/#proxybroker-authentication-plugin) to establish the identity of a client and then assign a *role token* (a string like `admin` or `app1`) to that client. This role token can represent a single client or multiple clients and is then used for [Authorization](security-authorization.md) to determine what the client is authorized to do. You can use roles to control per [...]
## Encryption
diff --git a/site2/website-next/versioned_docs/version-2.1.0-incubating/security-overview.md b/site2/website-next/versioned_docs/version-2.1.0-incubating/security-overview.md
index 6507a937339..8ed2d907d7a 100644
--- a/site2/website-next/versioned_docs/version-2.1.0-incubating/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.1.0-incubating/security-overview.md
@@ -21,7 +21,7 @@ It is strongly recommended to secure the service components in your Apache Pulsa
In Pulsar, a *role* is a string, like `admin` or `app1`, that can represent a single client or multiple clients. Roles are used to control permission for clients
to produce or consume from certain topics, administer the configuration for tenants, and more.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign that client a *role token*. This
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign that client a *role token*. This
role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication Providers
diff --git a/site2/website-next/versioned_docs/version-2.1.1-incubating/security-overview.md b/site2/website-next/versioned_docs/version-2.1.1-incubating/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.1.1-incubating/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.1.1-incubating/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-overview.md
index d03b8c85c38..93a766ee89f 100644
--- a/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-overview.md
index d03b8c85c38..93a766ee89f 100644
--- a/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.10.x/security-overview.md b/site2/website-next/versioned_docs/version-2.10.x/security-overview.md
index d03b8c85c38..93a766ee89f 100644
--- a/site2/website-next/versioned_docs/version-2.10.x/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.10.x/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.2.0/security-overview.md b/site2/website-next/versioned_docs/version-2.2.0/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.2.1/security-overview.md b/site2/website-next/versioned_docs/version-2.2.1/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.3.0/security-overview.md b/site2/website-next/versioned_docs/version-2.3.0/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.3.1/security-overview.md b/site2/website-next/versioned_docs/version-2.3.1/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.3.2/security-overview.md b/site2/website-next/versioned_docs/version-2.3.2/security-overview.md
index ad9a809e912..759ca8d7855 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/security-overview.md
@@ -21,7 +21,7 @@ It is strongly recommended to secure the service components in your Apache Pulsa
In Pulsar, a *role* is a string, like `admin` or `app1`, that can represent a single client or multiple clients. Roles are used to control permission for clients
to produce or consume from certain topics, administer the configuration for tenants, and more.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign that client a *role token*. This
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign that client a *role token*. This
role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication Providers
diff --git a/site2/website-next/versioned_docs/version-2.5.0/security-overview.md b/site2/website-next/versioned_docs/version-2.5.0/security-overview.md
index 91dc68e51d9..250db4f755b 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/security-overview.md
@@ -17,7 +17,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.5.1/security-overview.md b/site2/website-next/versioned_docs/version-2.5.1/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.5.2/security-overview.md b/site2/website-next/versioned_docs/version-2.5.2/security-overview.md
index 3f08cb29ad8..41beb0c8788 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/security-overview.md
@@ -20,7 +20,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.6.0/security-overview.md b/site2/website-next/versioned_docs/version-2.6.0/security-overview.md
index 91dc68e51d9..250db4f755b 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/security-overview.md
@@ -17,7 +17,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.6.1/security-overview.md b/site2/website-next/versioned_docs/version-2.6.1/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.6.2/security-overview.md b/site2/website-next/versioned_docs/version-2.6.2/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.6.3/security-overview.md b/site2/website-next/versioned_docs/version-2.6.3/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.6.4/security-overview.md b/site2/website-next/versioned_docs/version-2.6.4/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.0/security-overview.md b/site2/website-next/versioned_docs/version-2.7.0/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.1/security-overview.md b/site2/website-next/versioned_docs/version-2.7.1/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.2/security-overview.md b/site2/website-next/versioned_docs/version-2.7.2/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.3/security-overview.md b/site2/website-next/versioned_docs/version-2.7.3/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.4/security-overview.md b/site2/website-next/versioned_docs/version-2.7.4/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.7.5/security-overview.md b/site2/website-next/versioned_docs/version-2.7.5/security-overview.md
index a1664fcb8b4..6eb1e2d9309 100644
--- a/site2/website-next/versioned_docs/version-2.7.5/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.7.5/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.8.0-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.8.0-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.8.0-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.0-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.8.1-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.8.1-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.8.1-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.1-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.8.2-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.8.2-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.8.2-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.2-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.8.3-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.8.3-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.8.3-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.3-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.8.x/security-overview.md b/site2/website-next/versioned_docs/version-2.8.x/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.8.x/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.8.x/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.9.0-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.9.0-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.9.0-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.0-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.9.1-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.9.1-deprecated/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.9.1-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.1-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.9.2-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.9.2-deprecated/security-overview.md
index df630ab519b..a8120f984bf 100644
--- a/site2/website-next/versioned_docs/version-2.9.2-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.2-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.9.3-deprecated/security-overview.md b/site2/website-next/versioned_docs/version-2.9.3-deprecated/security-overview.md
index df630ab519b..a8120f984bf 100644
--- a/site2/website-next/versioned_docs/version-2.9.3-deprecated/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.3-deprecated/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers
diff --git a/site2/website-next/versioned_docs/version-2.9.x/security-overview.md b/site2/website-next/versioned_docs/version-2.9.x/security-overview.md
index 227dd5b5d4f..c6bd9b64e4f 100644
--- a/site2/website-next/versioned_docs/version-2.9.x/security-overview.md
+++ b/site2/website-next/versioned_docs/version-2.9.x/security-overview.md
@@ -21,7 +21,7 @@ You had better secure the service components in your Apache Pulsar deployment.
In Pulsar, a *role* is a string, like `admin` or `app1`, which can represent a single client or multiple clients. You can use roles to control permission for clients to produce or consume from certain topics, administer the configuration for tenants, and so on.
-Apache Pulsar uses a [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
+Apache Pulsar uses an [Authentication Provider](#authentication-providers) to establish the identity of a client and then assign a *role token* to that client. This role token is then used for [Authorization and ACLs](security-authorization.md) to determine what the client is authorized to do.
## Authentication providers