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/04/12 18:03:35 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#ec38211)
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 aacd25ffc9 Docs sync done from apache/pulsar(#ec38211)
aacd25ffc9 is described below
commit aacd25ffc9924d735a81a1315dc134d16f5ae416
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Tue Apr 12 18:03:29 2022 +0000
Docs sync done from apache/pulsar(#ec38211)
---
site2/docs/functions-worker.md | 4 ++--
site2/docs/reference-configuration.md | 2 +-
site2/docs/security-kerberos.md | 8 ++++----
site2/website-next/docs/functions-worker.md | 4 ++--
site2/website-next/docs/reference-configuration.md | 2 +-
site2/website-next/docs/security-kerberos.md | 8 ++++----
.../versioned_docs/version-2.5.0/security-kerberos.md | 8 ++++----
.../website-next/versioned_docs/version-2.5.1/functions-worker.md | 4 ++--
.../versioned_docs/version-2.5.1/security-kerberos.md | 8 ++++----
.../website-next/versioned_docs/version-2.5.2/functions-worker.md | 4 ++--
.../versioned_docs/version-2.5.2/security-kerberos.md | 8 ++++----
11 files changed, 30 insertions(+), 30 deletions(-)
diff --git a/site2/docs/functions-worker.md b/site2/docs/functions-worker.md
index c58d5a436d..85e636e8bf 100644
--- a/site2/docs/functions-worker.md
+++ b/site2/docs/functions-worker.md
@@ -195,13 +195,13 @@ authenticationEnabled: true
authenticationProviders: ['org.apache.pulsar.broker.authentication.AuthenticationProviderTls']
```
-For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasBrokerSectionName`
+For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasServerSectionName`
under `properties` if needed.
```
properties:
saslJaasClientAllowedIds: .*pulsar.*
- saslJaasBrokerSectionName: Broker
+ saslJaasServerSectionName: Broker
```
For *Token Authentication* provider, add necessary settings for `properties` if needed.
diff --git a/site2/docs/reference-configuration.md b/site2/docs/reference-configuration.md
index 1cdcb92447..af0f365656 100644
--- a/site2/docs/reference-configuration.md
+++ b/site2/docs/reference-configuration.md
@@ -597,7 +597,7 @@ You can set the log level and configuration in the [log4j2.yaml](https://github
|tokenAudienceClaim| The token audience "claim" name, e.g. "aud". It is used to get the audience from token. If it is not set, the audience is not verified. ||
| tokenAudience | The token audience stands for this broker. The field `tokenAudienceClaim` of a valid token need contains this parameter.| |
|saslJaasClientAllowedIds|This is a regexp, which limits the range of possible ids which can connect to the Broker using SASL. By default, it is set to `SaslConstants.JAAS_CLIENT_ALLOWED_IDS_DEFAULT`, which is ".*pulsar.*", so only clients whose id contains 'pulsar' are allowed to connect.|N/A|
-|saslJaasBrokerSectionName|Service Principal, for login context name. By default, it is set to `SaslConstants.JAAS_DEFAULT_BROKER_SECTION_NAME`, which is "Broker".|N/A|
+|saslJaasServerSectionName|Service Principal, for login context name. By default, it is set to `SaslConstants.JAAS_DEFAULT_BROKER_SECTION_NAME`, which is "Broker".|N/A|
|httpMaxRequestSize|If the value is larger than 0, it rejects all HTTP requests with bodies larged than the configured limit.|-1|
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats, set false to use published counter and consumed counter to calculate, this would be more efficient but may be inaccurate. |false|
|bookkeeperMetadataServiceUri|Metadata service uri is what BookKeeper used for loading corresponding metadata driver and resolving its metadata service location. This value can be fetched using `bookkeeper shell whatisinstanceid` command in BookKeeper cluster. For example: `zk+hierarchical://localhost:2181/ledgers`. The metadata service uri list can also be semicolon separated values like: `zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers`.|N/A|
diff --git a/site2/docs/security-kerberos.md b/site2/docs/security-kerberos.md
index f7fe4c5f65..897bf3bb0d 100644
--- a/site2/docs/security-kerberos.md
+++ b/site2/docs/security-kerberos.md
@@ -113,7 +113,7 @@ You can have 2 separate JAAS configuration files:
- Set `authenticationEnabled` to `true`;
- Set `authenticationProviders` to choose `AuthenticationProviderSasl`;
- Set `saslJaasClientAllowedIds` regex for principal that is allowed to connect to broker;
- - Set `saslJaasBrokerSectionName` that corresponds to the section in JAAS configuration file for broker;
+ - Set `saslJaasServerSectionName` that corresponds to the section in JAAS configuration file for broker;
To make Pulsar internal admin client work properly, you need to set the configuration in the `broker.conf` file as below:
- Set `brokerClientAuthenticationPlugin` to client plugin `AuthenticationSasl`;
@@ -125,7 +125,7 @@ You can have 2 separate JAAS configuration files:
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
## Authentication settings of the broker itself. Used when the broker connects to other brokers
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -306,7 +306,7 @@ In the `proxy.conf` file, set Kerberos related configuration. Here is an example
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarProxy
+saslJaasServerSectionName=PulsarProxy
## related to be authenticated by broker
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -326,7 +326,7 @@ The broker side configuration file is the same with the above `broker.conf`, you
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
```
## Regarding authorization and role token
diff --git a/site2/website-next/docs/functions-worker.md b/site2/website-next/docs/functions-worker.md
index 92ee57f744..849500e64f 100644
--- a/site2/website-next/docs/functions-worker.md
+++ b/site2/website-next/docs/functions-worker.md
@@ -230,14 +230,14 @@ authenticationProviders: ['org.apache.pulsar.broker.authentication.Authenticatio
```
-For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasBrokerSectionName`
+For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasServerSectionName`
under `properties` if needed.
```
properties:
saslJaasClientAllowedIds: .*pulsar.*
- saslJaasBrokerSectionName: Broker
+ saslJaasServerSectionName: Broker
```
diff --git a/site2/website-next/docs/reference-configuration.md b/site2/website-next/docs/reference-configuration.md
index f7d850ba74..f7601a0a7c 100644
--- a/site2/website-next/docs/reference-configuration.md
+++ b/site2/website-next/docs/reference-configuration.md
@@ -593,7 +593,7 @@ You can set the log level and configuration in the [log4j2.yaml](https://github
|tokenAudienceClaim| The token audience "claim" name, e.g. "aud". It is used to get the audience from token. If it is not set, the audience is not verified. ||
| tokenAudience | The token audience stands for this broker. The field `tokenAudienceClaim` of a valid token need contains this parameter.| |
|saslJaasClientAllowedIds|This is a regexp, which limits the range of possible ids which can connect to the Broker using SASL. By default, it is set to `SaslConstants.JAAS_CLIENT_ALLOWED_IDS_DEFAULT`, which is ".*pulsar.*", so only clients whose id contains 'pulsar' are allowed to connect.|N/A|
-|saslJaasBrokerSectionName|Service Principal, for login context name. By default, it is set to `SaslConstants.JAAS_DEFAULT_BROKER_SECTION_NAME`, which is "Broker".|N/A|
+|saslJaasServerSectionName|Service Principal, for login context name. By default, it is set to `SaslConstants.JAAS_DEFAULT_BROKER_SECTION_NAME`, which is "Broker".|N/A|
|httpMaxRequestSize|If the value is larger than 0, it rejects all HTTP requests with bodies larged than the configured limit.|-1|
|exposePreciseBacklogInPrometheus| Enable expose the precise backlog stats, set false to use published counter and consumed counter to calculate, this would be more efficient but may be inaccurate. |false|
|bookkeeperMetadataServiceUri|Metadata service uri is what BookKeeper used for loading corresponding metadata driver and resolving its metadata service location. This value can be fetched using `bookkeeper shell whatisinstanceid` command in BookKeeper cluster. For example: `zk+hierarchical://localhost:2181/ledgers`. The metadata service uri list can also be semicolon separated values like: `zk+hierarchical://zk1:2181;zk2:2181;zk3:2181/ledgers`.|N/A|
diff --git a/site2/website-next/docs/security-kerberos.md b/site2/website-next/docs/security-kerberos.md
index d765e3df07..7146b7858c 100644
--- a/site2/website-next/docs/security-kerberos.md
+++ b/site2/website-next/docs/security-kerberos.md
@@ -124,7 +124,7 @@ You can have 2 separate JAAS configuration files:
- Set `authenticationEnabled` to `true`;
- Set `authenticationProviders` to choose `AuthenticationProviderSasl`;
- Set `saslJaasClientAllowedIds` regex for principal that is allowed to connect to broker;
- - Set `saslJaasBrokerSectionName` that corresponds to the section in JAAS configuration file for broker;
+ - Set `saslJaasServerSectionName` that corresponds to the section in JAAS configuration file for broker;
To make Pulsar internal admin client work properly, you need to set the configuration in the `broker.conf` file as below:
- Set `brokerClientAuthenticationPlugin` to client plugin `AuthenticationSasl`;
@@ -137,7 +137,7 @@ You can have 2 separate JAAS configuration files:
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
## Authentication settings of the broker itself. Used when the broker connects to other brokers
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -344,7 +344,7 @@ In the `proxy.conf` file, set Kerberos related configuration. Here is an example
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarProxy
+saslJaasServerSectionName=PulsarProxy
## related to be authenticated by broker
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -366,7 +366,7 @@ The broker side configuration file is the same with the above `broker.conf`, you
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
```
diff --git a/site2/website-next/versioned_docs/version-2.5.0/security-kerberos.md b/site2/website-next/versioned_docs/version-2.5.0/security-kerberos.md
index d765e3df07..7146b7858c 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/security-kerberos.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/security-kerberos.md
@@ -124,7 +124,7 @@ You can have 2 separate JAAS configuration files:
- Set `authenticationEnabled` to `true`;
- Set `authenticationProviders` to choose `AuthenticationProviderSasl`;
- Set `saslJaasClientAllowedIds` regex for principal that is allowed to connect to broker;
- - Set `saslJaasBrokerSectionName` that corresponds to the section in JAAS configuration file for broker;
+ - Set `saslJaasServerSectionName` that corresponds to the section in JAAS configuration file for broker;
To make Pulsar internal admin client work properly, you need to set the configuration in the `broker.conf` file as below:
- Set `brokerClientAuthenticationPlugin` to client plugin `AuthenticationSasl`;
@@ -137,7 +137,7 @@ You can have 2 separate JAAS configuration files:
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
## Authentication settings of the broker itself. Used when the broker connects to other brokers
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -344,7 +344,7 @@ In the `proxy.conf` file, set Kerberos related configuration. Here is an example
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarProxy
+saslJaasServerSectionName=PulsarProxy
## related to be authenticated by broker
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -366,7 +366,7 @@ The broker side configuration file is the same with the above `broker.conf`, you
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
```
diff --git a/site2/website-next/versioned_docs/version-2.5.1/functions-worker.md b/site2/website-next/versioned_docs/version-2.5.1/functions-worker.md
index 92ee57f744..849500e64f 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/functions-worker.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/functions-worker.md
@@ -230,14 +230,14 @@ authenticationProviders: ['org.apache.pulsar.broker.authentication.Authenticatio
```
-For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasBrokerSectionName`
+For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasServerSectionName`
under `properties` if needed.
```
properties:
saslJaasClientAllowedIds: .*pulsar.*
- saslJaasBrokerSectionName: Broker
+ saslJaasServerSectionName: Broker
```
diff --git a/site2/website-next/versioned_docs/version-2.5.1/security-kerberos.md b/site2/website-next/versioned_docs/version-2.5.1/security-kerberos.md
index d765e3df07..7146b7858c 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/security-kerberos.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/security-kerberos.md
@@ -124,7 +124,7 @@ You can have 2 separate JAAS configuration files:
- Set `authenticationEnabled` to `true`;
- Set `authenticationProviders` to choose `AuthenticationProviderSasl`;
- Set `saslJaasClientAllowedIds` regex for principal that is allowed to connect to broker;
- - Set `saslJaasBrokerSectionName` that corresponds to the section in JAAS configuration file for broker;
+ - Set `saslJaasServerSectionName` that corresponds to the section in JAAS configuration file for broker;
To make Pulsar internal admin client work properly, you need to set the configuration in the `broker.conf` file as below:
- Set `brokerClientAuthenticationPlugin` to client plugin `AuthenticationSasl`;
@@ -137,7 +137,7 @@ You can have 2 separate JAAS configuration files:
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
## Authentication settings of the broker itself. Used when the broker connects to other brokers
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -344,7 +344,7 @@ In the `proxy.conf` file, set Kerberos related configuration. Here is an example
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarProxy
+saslJaasServerSectionName=PulsarProxy
## related to be authenticated by broker
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -366,7 +366,7 @@ The broker side configuration file is the same with the above `broker.conf`, you
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
```
diff --git a/site2/website-next/versioned_docs/version-2.5.2/functions-worker.md b/site2/website-next/versioned_docs/version-2.5.2/functions-worker.md
index 92ee57f744..849500e64f 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/functions-worker.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/functions-worker.md
@@ -230,14 +230,14 @@ authenticationProviders: ['org.apache.pulsar.broker.authentication.Authenticatio
```
-For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasBrokerSectionName`
+For *SASL Authentication* provider, add `saslJaasClientAllowedIds` and `saslJaasServerSectionName`
under `properties` if needed.
```
properties:
saslJaasClientAllowedIds: .*pulsar.*
- saslJaasBrokerSectionName: Broker
+ saslJaasServerSectionName: Broker
```
diff --git a/site2/website-next/versioned_docs/version-2.5.2/security-kerberos.md b/site2/website-next/versioned_docs/version-2.5.2/security-kerberos.md
index d765e3df07..7146b7858c 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/security-kerberos.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/security-kerberos.md
@@ -124,7 +124,7 @@ You can have 2 separate JAAS configuration files:
- Set `authenticationEnabled` to `true`;
- Set `authenticationProviders` to choose `AuthenticationProviderSasl`;
- Set `saslJaasClientAllowedIds` regex for principal that is allowed to connect to broker;
- - Set `saslJaasBrokerSectionName` that corresponds to the section in JAAS configuration file for broker;
+ - Set `saslJaasServerSectionName` that corresponds to the section in JAAS configuration file for broker;
To make Pulsar internal admin client work properly, you need to set the configuration in the `broker.conf` file as below:
- Set `brokerClientAuthenticationPlugin` to client plugin `AuthenticationSasl`;
@@ -137,7 +137,7 @@ You can have 2 separate JAAS configuration files:
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
## Authentication settings of the broker itself. Used when the broker connects to other brokers
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -344,7 +344,7 @@ In the `proxy.conf` file, set Kerberos related configuration. Here is an example
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarProxy
+saslJaasServerSectionName=PulsarProxy
## related to be authenticated by broker
brokerClientAuthenticationPlugin=org.apache.pulsar.client.impl.auth.AuthenticationSasl
@@ -366,7 +366,7 @@ The broker side configuration file is the same with the above `broker.conf`, you
authenticationEnabled=true
authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderSasl
saslJaasClientAllowedIds=.*client.*
-saslJaasBrokerSectionName=PulsarBroker
+saslJaasServerSectionName=PulsarBroker
```