Unable to connect to Kafka with SASL_SSL + SCRAM

Connector Questions & Issues
,
5

So, I found out some kind of workaround for that:

  1. I put my certificate in this image - airbyte/airbyte-integrations/connectors/destination-kafka at master · airbytehq/airbyte · GitHub by adding these lines to Dockerfile:
COPY ./certnew.cer $JAVA_HOME/lib/security/
RUN cd $JAVA_HOME/lib/security/ && keytool -import -trustcacerts -alias <your_alias> -file certnew.cer -cacerts -storepass <your_password> -noprompt
  1. Then it’s necessary to run gradle build for this module because image uses compiled binaries in line ADD bin/${APPLICATION}-${VERSION}.tar /app. I found out that this action requires latest versions of gradle and java to work, so keep attention for that
  2. Finally I built local image and tagged it to force docker to use it instead of getting one from repo
docker build -t airbyte/destination-kafka:<latest_image_version>  .

And now when creating Kafka-destination I’m able to get through SSL handshake and successfully passing the topic creation test. The only thing left to worry about is that user mentioned in sasl.jaas.config should have rights to create topics and write to them at this Kafka-server.
Hope it helps somebody with similar problem