Open JoschaLaubach opened 4 months ago
Is there some config we're missing? Any help is welcome!
No, no config missing, this is a bug in the implementation. When plain is used the JaasClientOauthLoginCallbackHandler
should not be used, but it's still being forced.
It worked for me in 2.6.5.Final when set the CallbackHandler to the following value: REGISTRY_KAFKA_COMMON_SASL_LOGIN_CALLBACK_HANDLER_CLASS=org.apache.kafka.common.security.authenticator.SaslClientCallbackHandler
Description
Registry Version: 2.5.8.Final Persistence type: kafkasql
We're trying to use our Kafka cluster as a persistence backend. Login to the cluster requires SASL/PLAIN via SSL. We try to set everything via env vars in the Pod that apicurio-registry is running in.
Environment
Running on Kubernetes 1.29.4
Steps to Reproduce
We set the following env vars:
We also tried to unset the JaasClientOauthLoginCallbackHandler, but it didn't work:
Expected vs Actual Behaviour
Login via SASL/PLAIN to Kafka cluster works, but instead we get an error. It seems the defaults here are set to use OAUTHBEARER, but our cluster doesn't use that. At least the CallbackHandler is still being used. We get the error Unexpected SASL mechanism: PLAIN.
Logs