KafkaConnector authentication with Apicurio Azure AD #6036
-
DescriptionHi, I am using Debezium in OpenShift with Apicurio (redhat flavor for both of them). I have configured a KafkaConnector to use the schema registry and it need to login with oauth through Azure. It seems that KafkaConnector doesn't do the authentication and therefore doesn't have access to the registry. In the firewall or proxy log, there is no connection to Azure AD when the KafkaConnector is running. (if there is no connection the authentication cannot be working for me) I have followed https://www.apicur.io/blog/2024/09/23/registry-azure-entraid-tutorial and with the same clientID that use KafkaConnector I can interact with the API. So it seems that the Apicurio side is working correctly with Azure. EnvironmentOpenShift 4.16 Steps to ReproduceKafkaConnector configuration :
But it doesn't work. I can see in the log of Apicurio after enabling the debug log when the KafkaConnector is configured:
And this is the log on KafkaConnector side:
Expected vs Actual BehaviourKafkaConnector doesn't do the authentication |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I have managed to get some traffic log between the KafkaConnect pod and the registry:
And as I presume, there is not authentication header during the POST so Apicurio return a 401. |
Beta Was this translation helpful? Give feedback.
-
The underlying issue might be that you're using the configuration values from 3.x in a 2.6.x deployment. The correct configuration paths in 2.6 are:
(Note that I have removed .registry from the path). |
Beta Was this translation helpful? Give feedback.
The underlying issue might be that you're using the configuration values from 3.x in a 2.6.x deployment.
The correct configuration paths in 2.6 are:
(Note that I have removed .registry from the path).