michaeljmarshall opened a new pull request, #19026: URL: https://github.com/apache/pulsar/pull/19026
Master Issue: #10816 ### Motivation In issue #10816, we see that a new lookup command triggers auth failure. In reading through the solution from #17831, I noticed that we are still open to a specific kind of failure. Specifically, the auth data for a client is stored indefinitely in the proxy. As a result, when the proxy attempts to make a new connection to a broker for a lookup, then the auth data may be expired. ### Modifications * Update the `clientAuthData` when the client sends it. This solution does not cover the case where the data is still out of date, so I may look at finding a better solution. ### Verifying this change I will work on a test for this change. ### Does this pull request potentially affect one of the following parts: This solution restores expected functionality for the ability to refresh authentication data seamlessly when using the proxy. ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. Please attach the local preview screenshots (run `sh start.sh` at `pulsar/site2/website`) to your PR description, or else your PR might not get merged. --> - [x] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> ### Matching PR in forked repository PR in forked repository: https://github.com/michaeljmarshall/pulsar/pull/9 -- 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]
