Hello, I'm facing a new issue on the 3.0.5 of Pulsar

2024-06-11T14:33:16.540453842Z javax.naming.AuthenticationException: Failed to authentication token: JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.
	at org.apache.pulsar.broker.authentication.AuthenticationProviderToken.authenticateToken(AuthenticationProviderToken.java:276) ~[org.apache.pulsar-pulsar-broker-common-3.0.5.jar:3.0.5]
2024-06-11T14:33:16.540460044Z 	at org.apache.pulsar.broker.authentication.AuthenticationProviderToken$TokenAuthenticationState.checkExpiration(AuthenticationProviderToken.java:414) ~[org.apache.pulsar-pulsar-broker-common-3.0.5.jar:3.0.5]
	at org.apache.pulsar.broker.authentication.AuthenticationProviderToken$TokenAuthenticationState.authenticate(AuthenticationProviderToken.java:408) ~[org.apache.pulsar-pulsar-broker-common-3.0.5.jar:3.0.5]
2024-06-11T14:33:16.540465092Z 	at org.apache.pulsar.broker.authentication.AuthenticationState.authenticateAsync(AuthenticationState.java:69) ~[org.apache.pulsar-pulsar-broker-common-3.0.5.jar:3.0.5]

I tried to reinstall Pulsar with the same config and use the script prepare_helm_release.sh but it change nothing

Which Apache Pulsar Helm chart version are you using? Latest 3.4.1 ? Please report an issue at https://github.com/apache/pulsar-helm-chart/issues with steps to reproduce

Thanks Lari for the answer, I finally found the problem when producing a message without secured it on the pulsar connector