isminexxb commented on issue #17540: URL: https://github.com/apache/pulsar/issues/17540#issuecomment-1241406187
> > > Only Pulsar 2.11 supports JWT with TLS transport, you need to use the TLS authentication now. > > > > > > Did you mean [#15289](https://github.com/apache/pulsar/issues/15289)? Does it still not support the proxy and c++ library? In addition, will JWT authorization be supported for proxy then? @nodece > > I improved the broker and proxy, but the CPP client misses this improvement, I can make a PR to improve that. Nice to hear that. But when I use JWT with proxy only (Broker works without any authentication or authorization configuration. Proxy configures with authorizationEnabled=true but does not forward authorization credentials to brokers), the client can still produce messages without privilege. I also haven't found related authorization check in proxy's implementation or proxy's log. Is this usage not supported now? -- 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]
