You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/12/21 23:07:31 UTC

[GitHub] [pulsar] michaeljmarshall commented on issue #10816: PulsarProxy does not always refresh authentication tokens received from client

michaeljmarshall commented on issue #10816:
URL: https://github.com/apache/pulsar/issues/10816#issuecomment-1362204702

   I agree with @lhotari that the solution in https://github.com/apache/pulsar/pull/17831 will lead to corruption.
   
   To take a step back, I think we need to clarify what the actual issue. Once the client's connection through the proxy is established with the broker, the broker's auth refresh challenge protocol takes over, assuming everything is configured correctly.
   
   What appears to be the problem is that the `clientAuthData` in the `ProxyConnection` is never updated. That means the `clientCnxSupplier` will have stale data when making connections to new brokers. I'll try to put together a PR to show a solution.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org