damienburke commented on issue #22125: URL: https://github.com/apache/pulsar/issues/22125#issuecomment-1994106847
Just also to restate some of what u said - just for my own understanding - if u can confirm if accurate @nodece? When the pulsar broker identifies that the authenticated credentials have expired - and it issues the challenge to the client to refresh their credentials (e.g. as supported by "token" auth method - and as triggered by `authenticationRefreshCheckSeconds`) - the client uses the **same** TCP connection, with the **same** TLS encryption to send their refreshed credentials. Whereas your point if that, if the client (or sever?) cert has expired - the client needs to make a new TCP connection (and negotiate TLS) again. -- 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
