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/09/20 18:02:18 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#72dd01b)
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 0bd69e5f808 Docs sync done from apache/pulsar(#72dd01b)
0bd69e5f808 is described below
commit 0bd69e5f80858d311ae86dcc19ba392614bc7055
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Tue Sep 20 18:02:13 2022 +0000
Docs sync done from apache/pulsar(#72dd01b)
---
site2/website-next/docs/security-oauth2.md | 2 +-
site2/website-next/static/swagger/restApiVersions.json | 4 ++--
.../versioned_docs/version-2.10.0-deprecated/security-oauth2.md | 2 +-
.../versioned_docs/version-2.10.1-deprecated/security-oauth2.md | 2 +-
site2/website-next/versioned_docs/version-2.10.x/security-oauth2.md | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/site2/website-next/docs/security-oauth2.md b/site2/website-next/docs/security-oauth2.md
index 649bac85af9..88b1506398d 100644
--- a/site2/website-next/docs/security-oauth2.md
+++ b/site2/website-next/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-next/static/swagger/restApiVersions.json b/site2/website-next/static/swagger/restApiVersions.json
index 29099ec9b0e..26ea08d1fcf 100644
--- a/site2/website-next/static/swagger/restApiVersions.json
+++ b/site2/website-next/static/swagger/restApiVersions.json
@@ -97,7 +97,7 @@
]
}
],
- "2.4.1": [
+ "2.4.2": [
{
"version": "v2",
"fileName": [
@@ -113,7 +113,7 @@
]
}
],
- "2.4.2": [
+ "2.4.1": [
{
"version": "v2",
"fileName": [
diff --git a/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-oauth2.md b/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website-next/versioned_docs/version-2.10.0-deprecated/security-oauth2.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.10.1-deprecated/security-oauth2.md b/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website-next/versioned_docs/version-2.10.1-deprecated/security-oauth2.md
+++ b/site2/website-next/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-next/versioned_docs/version-2.10.x/security-oauth2.md b/site2/website-next/versioned_docs/version-2.10.x/security-oauth2.md
index d32568c8c1f..4ff8bf10b38 100644
--- a/site2/website-next/versioned_docs/version-2.10.x/security-oauth2.md
+++ b/site2/website-next/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`.