nodece commented on code in PR #15799: URL: https://github.com/apache/pulsar/pull/15799#discussion_r882358300
########## site2/docs/security-extending.md: ########## @@ -52,7 +52,19 @@ authenticationProviders= ``` -For the implementation of the `org.apache.pulsar.broker.authentication.AuthenticationProvider` interface, refer to [here](https://github.com/apache/pulsar/blob/master/pulsar-broker-common/src/main/java/org/apache/pulsar/broker/authentication/AuthenticationProvider.java). +:::tip + +Pulsar supports an authentication provider chain that contains multiple authentication providers with the same authentication method name. + +For example, your Pulsar cluster uses JSON Web Token (JWT) authentication and you want to upgrade it to use OAuth2.0 authentication. Both JWT and OAuth2.0 share the same authentication method name. In this case, you can chain the two class names in `authenticationProviders` and separate them by using a comma. + +```properties +authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderJWT,org.apache.pulsar.broker.authentication.AuthenticationProviderOAuth2 Review Comment: > The motivation of #9094 is that since we can implement our own `AuthenticationProvider`, for example, we can implements `AuthenticationProviderOAuth2` whose auth name is also "token" in future, at that time we can configure both `AuthenticationProviderOAuth2` and `AuthenticationProviderToken`. This is right. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
