beyondyinjl2 commented on pull request #12331: URL: https://github.com/apache/pulsar/pull/12331#issuecomment-940895526
> Is it necessary? Currently KoP has implemented the authorization by leveraging Pulsar broker's authorization but doesn't require the access permission for this field. There is authentication when the mqtt protocol is connected, but the permission control of publishing and subscribing to topics is not implemented, and any user has the permission to publish and subscribe to topics When mop is connected for authentication, it uses: io.streamnative.pulsar.handlers.mqtt.utils.AuthUtils class configureAuthProviders() method, where AuthenticationService authService uses final AuthenticationProvider authProvider = authService.getAuthenticationProvider(authMethod); At present, mop does not have the authority to publish and subscribe to topics. I want to refer to the authentication method to implement the authority control of publishing and subscribing to topics, AuthorizationService authzService to obtain final AuthorizationProvider authzProvider = authzService.getProvider(); -- 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]
