acortes-okode commented on issue #16626: URL: https://github.com/apache/pulsar/issues/16626#issuecomment-1186951075
Hi again @nodece, I managed to run websocket service as a separate component by running first Pulsar in standalone mode with `webSocketServiceEnabled=false` and then starting `bin/pulsar websocket` configuring the `websocket.conf` with the same authentication/authorization parameters and with the `medatadastore` and `pulsar-cluster` parameters to reference the standalone Pulsar instance. As you pointed out, I was able to authenticate and authorize correctly with the `token` request parameter this way! So it seems the issue does only occur if the websocket service is enabled in the broker and the AuthenticationFilter gets in the way. I'm gonna change the issue's title to reflect that. Or let me know whatever you consider I should do (close, open a new one...) Thanks again! -- 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]
