You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ju...@apache.org on 2022/09/20 13:11:43 UTC
[pulsar] branch master updated: [Doc]--remove redundant words (#17741)
This is an automated email from the ASF dual-hosted git repository.
junma pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new f267ef39f10 [Doc]--remove redundant words (#17741)
f267ef39f10 is described below
commit f267ef39f10d016de8f84f40d345d5e458f0d51f
Author: Huanli Meng <48...@users.noreply.github.com>
AuthorDate: Tue Sep 20 21:11:35 2022 +0800
[Doc]--remove redundant words (#17741)
---
site2/docs/security-oauth2.md | 2 +-
.../website/versioned_docs/version-2.10.0-deprecated/security-oauth2.md | 2 +-
.../website/versioned_docs/version-2.10.1-deprecated/security-oauth2.md | 2 +-
site2/website/versioned_docs/version-2.10.x/security-oauth2.md | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/site2/docs/security-oauth2.md b/site2/docs/security-oauth2.md
index 649bac85af9..88b1506398d 100644
--- a/site2/docs/security-oauth2.md
+++ b/site2/docs/security-oauth2.md
@@ -32,7 +32,7 @@ The following table lists parameters supported for the `client credentials` auth
| `issuerUrl` | URL of the authentication provider which allows the Pulsar client to obtain an access token | `https://accounts.google.com` | Required |
| `privateKey` | URL to a JSON credentials file | Support the following pattern formats: <br /> <li> `file:///path/to/file` </li><li>`file:/path/to/file` </li><li> `data:application/json;base64,<base64-encoded value>` </li>| Required |
| `audience` | An OAuth 2.0 "resource server" identifier for the Pulsar cluster | `https://broker.example.com` | Optional |
-| `scope` | Scope of an access request. <br />For more more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
+| `scope` | Scope of an access request. <br />For more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
The credentials file contains service account credentials used with the client authentication type. The following shows an example of a credentials file `credentials_file.json`.
diff --git a/site2/website/versioned_docs/version-2.10.0-deprecated/security-oauth2.md b/site2/website/versioned_docs/version-2.10.0-deprecated/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website/versioned_docs/version-2.10.0-deprecated/security-oauth2.md
+++ b/site2/website/versioned_docs/version-2.10.0-deprecated/security-oauth2.md
@@ -33,7 +33,7 @@ The following table lists parameters supported for the `client credentials` auth
| `issuerUrl` | URL of the authentication provider which allows the Pulsar client to obtain an access token | `https://accounts.google.com` | Required |
| `privateKey` | URL to a JSON credentials file | Support the following pattern formats: <br /> <li> `file:///path/to/file` </li><li>`file:/path/to/file` </li><li> `data:application/json;base64,<base64-encoded value>` </li>| Required |
| `audience` | An OAuth 2.0 "resource server" identifier for the Pulsar cluster | `https://broker.example.com` | Optional |
-| `scope` | Scope of an access request. <br />For more more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
+| `scope` | Scope of an access request. <br />For more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
The credentials file contains service account credentials used with the client authentication type. The following shows an example of a credentials file `credentials_file.json`.
diff --git a/site2/website/versioned_docs/version-2.10.1-deprecated/security-oauth2.md b/site2/website/versioned_docs/version-2.10.1-deprecated/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website/versioned_docs/version-2.10.1-deprecated/security-oauth2.md
+++ b/site2/website/versioned_docs/version-2.10.1-deprecated/security-oauth2.md
@@ -33,7 +33,7 @@ The following table lists parameters supported for the `client credentials` auth
| `issuerUrl` | URL of the authentication provider which allows the Pulsar client to obtain an access token | `https://accounts.google.com` | Required |
| `privateKey` | URL to a JSON credentials file | Support the following pattern formats: <br /> <li> `file:///path/to/file` </li><li>`file:/path/to/file` </li><li> `data:application/json;base64,<base64-encoded value>` </li>| Required |
| `audience` | An OAuth 2.0 "resource server" identifier for the Pulsar cluster | `https://broker.example.com` | Optional |
-| `scope` | Scope of an access request. <br />For more more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
+| `scope` | Scope of an access request. <br />For more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
The credentials file contains service account credentials used with the client authentication type. The following shows an example of a credentials file `credentials_file.json`.
diff --git a/site2/website/versioned_docs/version-2.10.x/security-oauth2.md b/site2/website/versioned_docs/version-2.10.x/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website/versioned_docs/version-2.10.x/security-oauth2.md
+++ b/site2/website/versioned_docs/version-2.10.x/security-oauth2.md
@@ -33,7 +33,7 @@ The following table lists parameters supported for the `client credentials` auth
| `issuerUrl` | URL of the authentication provider which allows the Pulsar client to obtain an access token | `https://accounts.google.com` | Required |
| `privateKey` | URL to a JSON credentials file | Support the following pattern formats: <br /> <li> `file:///path/to/file` </li><li>`file:/path/to/file` </li><li> `data:application/json;base64,<base64-encoded value>` </li>| Required |
| `audience` | An OAuth 2.0 "resource server" identifier for the Pulsar cluster | `https://broker.example.com` | Optional |
-| `scope` | Scope of an access request. <br />For more more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
+| `scope` | Scope of an access request. <br />For more information, see [access token scope](https://datatracker.ietf.org/doc/html/rfc6749#section-3.3). | api://pulsar-cluster-1/.default | Optional |
The credentials file contains service account credentials used with the client authentication type. The following shows an example of a credentials file `credentials_file.json`.