nodece commented on code in PR #15799: URL: https://github.com/apache/pulsar/pull/15799#discussion_r883712706
########## site2/docs/security-extending.md: ########## @@ -56,10 +56,10 @@ authenticationProviders= 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. +For example, your Pulsar cluster uses JSON Web Token (JWT) authentication (with an authentication method named `token`) and you want to upgrade it to use OAuth2.0 authentication with the same authentication name. In this case, you can implement your own authentication provider `AuthenticationProviderOAuth2` and configure `authenticationProviders` as follows. Review Comment: Can you explain how it is authentication? For example, when you request the broker using the token authentication method, the broker will find the providers with the same authentication method to authenticate. -- 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]
