Joshhw opened a new issue #7830: URL: https://github.com/apache/pulsar/issues/7830
**Describe the bug** When trying to connect to the brokers through the pulsar proxy component using the binary connection the client's `authenticationDataSource` is not being forwarded to the broker for Authorization. When changing the `brokerServiceUrl` to `http://pulsar-proxy:80/` it seems to work with the client credentials but doesn't use the proxy token. I've tested this by executing into the toolset container. I've gotten to to work by connecting directly to the broker with the `---url` via the pulsar-client. **To Reproduce** Steps to reproduce the behavior: 1. configure the default helm charts to forward the client creds for the proxy 2. configure a custom authN/authZ within the helm charts 3. put some logs in your authZ methods and print the `AuthenticationDataSource` that is coming into your methods. 4. watch it not work. **Expected behavior** I expect the authenticationDataSource for the proxy and the client should be passing through the AuthorizationProvider methods. **Additional context** This [thread](https://apache-pulsar.slack.com/archives/C5Z4T36F7/p1597261747377100) ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
