damienburke commented on issue #22125: URL: https://github.com/apache/pulsar/issues/22125#issuecomment-1980615861
Thanks for the feedback @lhotari, and link to related [PR](https://github.com/apache/pulsar/pull/13951). Reviewing said PR, that functionality sounds very useful. As a first step, my pref is for mTLS to have parity with the existing token refresh logic - i.e. all server side driven - as per `authenticationRefreshCheckSeconds`. I have a PoC mostly working and can share my approach in next couple of days. Does it sound reasonable to keep the scope of my issue as is? Fyi, with our infrastructure (Vault & Consul), we already have the ability to rotate auth credentials before they actually expire (and make them available to the pulsar clients apps). Also, we are polyglot env, and therefore would prob leverage this approach, even if the Java client supported this. -- 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-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
