naahk37 opened a new issue, #25074: URL: https://github.com/apache/pulsar/issues/25074
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Pulsar Version: 4.0.7 (3 broker, 3 bookies, 3 zookeeper) OS: Ubuntu 24.04 Java: OpenJDK 21.0.8 Broker Client Authentication is enabled, for the brokers as well as for the function workers (running with the brokers) ### Issue Description One of our brokers restarted and wasn't able to authenticate anymore. I'm not sure, but I think it's actually the function worker client that cannot authenticate, because when I start the broker with disabled function workers, it works. I pasted error code below and uploaded the stacktrace. We recently deployed a new function, but the cluster was running without any problems since then. I'm not sure if those two things correlate.. ### Error messages ```text Message: Topic creation encountered an exception by initialize topic policies service. topic_name=persistent://public/functions/assignments error_message=java.lang.RuntimeException: java.lang.RuntimeException: org.apache.pulsar.broker.PulsarServerException: org.apache.pulsar.client.api.PulsarClientException$AuthenticationException: Unable to retrieve OAuth 2.0 server metadata ``` ### Reproducing the issue I tried to restart the second broker to see if the problem is maybe constrained only to one machine, but it's the same with this broker too.. ### Additional information [pulsar_oauth_problem.txt](https://github.com/user-attachments/files/24160428/pulsar_oauth_problem.txt) ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
