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 03b3e7f Docs sync done from apache/pulsar(#b5b0967)
03b3e7f is described below
commit 03b3e7fb55e3110381d542b52c51512db816a0aa
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Thu Mar 24 12:07:14 2022 +0000
Docs sync done from apache/pulsar(#b5b0967)
---
site2/docs/security-authorization.md | 14 ++++++++++++++
site2/website-next/docs/security-authorization.md | 16 ++++++++++++++++
.../version-2.2.0/security-authorization.md | 16 ++++++++++++++++
.../version-2.2.1/security-authorization.md | 16 ++++++++++++++++
.../version-2.3.1/security-authorization.md | 16 ++++++++++++++++
.../version-2.3.2/security-authorization.md | 16 ++++++++++++++++
.../version-2.4.0/security-authorization.md | 16 ++++++++++++++++
.../version-2.5.0/security-authorization.md | 16 ++++++++++++++++
.../version-2.5.1/security-authorization.md | 16 ++++++++++++++++
.../version-2.5.2/security-authorization.md | 16 ++++++++++++++++
.../version-2.8.1/security-authorization.md | 16 ++++++++++++++++
.../version-2.8.2/security-authorization.md | 16 ++++++++++++++++
.../version-2.9.0/security-authorization.md | 16 ++++++++++++++++
.../version-2.9.1/security-authorization.md | 16 ++++++++++++++++
.../version-2.8.1/security-authorization.md | 14 ++++++++++++++
.../version-2.8.2/security-authorization.md | 14 ++++++++++++++
.../version-2.9.0/security-authorization.md | 14 ++++++++++++++
.../version-2.9.1/security-authorization.md | 14 ++++++++++++++
18 files changed, 278 insertions(+)
diff --git a/site2/docs/security-authorization.md
b/site2/docs/security-authorization.md
index 23ac79c..1046190 100644
--- a/site2/docs/security-authorization.md
+++ b/site2/docs/security-authorization.md
@@ -98,3 +98,17 @@ PulsarAdmin admin = PulsarAdmin.builder()
.tlsTrustCertsFilePath("/path/to/trust/cert")
.build();
```
+
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt.md).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+```
\ No newline at end of file
diff --git a/site2/website-next/docs/security-authorization.md
b/site2/website-next/docs/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/docs/security-authorization.md
+++ b/site2/website-next/docs/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.2.0/security-authorization.md
b/site2/website-next/versioned_docs/version-2.2.0/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.2.1/security-authorization.md
b/site2/website-next/versioned_docs/version-2.2.1/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.3.1/security-authorization.md
b/site2/website-next/versioned_docs/version-2.3.1/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.3.2/security-authorization.md
b/site2/website-next/versioned_docs/version-2.3.2/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.4.0/security-authorization.md
b/site2/website-next/versioned_docs/version-2.4.0/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.5.0/security-authorization.md
b/site2/website-next/versioned_docs/version-2.5.0/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.5.1/security-authorization.md
b/site2/website-next/versioned_docs/version-2.5.1/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.5.2/security-authorization.md
b/site2/website-next/versioned_docs/version-2.5.2/security-authorization.md
index b1003d2..d9d3366 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/security-authorization.md
@@ -111,3 +111,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.8.1/security-authorization.md
b/site2/website-next/versioned_docs/version-2.8.1/security-authorization.md
index e678587..cc9c03d 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/security-authorization.md
@@ -112,3 +112,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.8.2/security-authorization.md
b/site2/website-next/versioned_docs/version-2.8.2/security-authorization.md
index e678587..cc9c03d 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/security-authorization.md
@@ -112,3 +112,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.9.0/security-authorization.md
b/site2/website-next/versioned_docs/version-2.9.0/security-authorization.md
index e678587..cc9c03d 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/security-authorization.md
@@ -112,3 +112,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website-next/versioned_docs/version-2.9.1/security-authorization.md
b/site2/website-next/versioned_docs/version-2.9.1/security-authorization.md
index e678587..cc9c03d 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/security-authorization.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/security-authorization.md
@@ -112,3 +112,19 @@ PulsarAdmin admin = PulsarAdmin.builder()
```
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+
+ ```
+
diff --git
a/site2/website/versioned_docs/version-2.8.1/security-authorization.md
b/site2/website/versioned_docs/version-2.8.1/security-authorization.md
index 73f875d..1763220 100644
--- a/site2/website/versioned_docs/version-2.8.1/security-authorization.md
+++ b/site2/website/versioned_docs/version-2.8.1/security-authorization.md
@@ -99,3 +99,17 @@ PulsarAdmin admin = PulsarAdmin.builder()
.tlsTrustCertsFilePath("/path/to/trust/cert")
.build();
```
+
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt.md).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+```
\ No newline at end of file
diff --git
a/site2/website/versioned_docs/version-2.8.2/security-authorization.md
b/site2/website/versioned_docs/version-2.8.2/security-authorization.md
index 1519d12..d8e90b0 100644
--- a/site2/website/versioned_docs/version-2.8.2/security-authorization.md
+++ b/site2/website/versioned_docs/version-2.8.2/security-authorization.md
@@ -99,3 +99,17 @@ PulsarAdmin admin = PulsarAdmin.builder()
.tlsTrustCertsFilePath("/path/to/trust/cert")
.build();
```
+
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt.md).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+```
\ No newline at end of file
diff --git
a/site2/website/versioned_docs/version-2.9.0/security-authorization.md
b/site2/website/versioned_docs/version-2.9.0/security-authorization.md
index 2b726e5..fe96577 100644
--- a/site2/website/versioned_docs/version-2.9.0/security-authorization.md
+++ b/site2/website/versioned_docs/version-2.9.0/security-authorization.md
@@ -99,3 +99,17 @@ PulsarAdmin admin = PulsarAdmin.builder()
.tlsTrustCertsFilePath("/path/to/trust/cert")
.build();
```
+
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt.md).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+```
\ No newline at end of file
diff --git
a/site2/website/versioned_docs/version-2.9.1/security-authorization.md
b/site2/website/versioned_docs/version-2.9.1/security-authorization.md
index 091ddac..4b9a0cb 100644
--- a/site2/website/versioned_docs/version-2.9.1/security-authorization.md
+++ b/site2/website/versioned_docs/version-2.9.1/security-authorization.md
@@ -99,3 +99,17 @@ PulsarAdmin admin = PulsarAdmin.builder()
.tlsTrustCertsFilePath("/path/to/trust/cert")
.build();
```
+
+## Authorize an authenticated client with multiple roles
+
+When a client is identified with multiple roles in a token (the type of role
claim in the token is an array) during the authentication process, Pulsar
supports to check the permissions of all the roles and further authorize the
client as long as one of its roles has the required permissions.
+
+> **Note**<br />
+> This authorization method is only compatible with [JWT
authentication](security-jwt.md).
+
+To enable this authorization method, configure the authorization provider as
`MultiRolesTokenAuthorizationProvider` in the `conf/broker.conf` file.
+
+ ```properties
+ # Authorization provider fully qualified class-name
+
authorizationProvider=org.apache.pulsar.broker.authorization.MultiRolesTokenAuthorizationProvider
+```
\ No newline at end of file
