Debezium Kafka Connect no longer properly parsing sasl jaas config

[Brandon Harvey]

Hello,

We've run into an issue with the Debezium kafka-connect docker image 1.4.2.Final (https://hub.docker.com/layers/debezium/connect/1.4.2.Final/images/sha256-f14e176ecbf367e70149c6ffbe93ab4d734785c53527eeedaf4384f565e2e882?context=explore). It appears that it is no longer parsing the provided sasl.jaas.config environment variable. The parsing works fine in 1.4.1.Final but appears to be broken from 1.4.2.Final and onwards.

We're providing the following environment variable:

CONNECT_SASL_JAAS_CONFIG: org.apache.kafka.common.security.scram.ScramLoginModule required username="fakeusername" password="fakepassword"

In 1.4.1.Final this is properly parsed out as seen by the following output:

--- Setting property from CONNECT_SASL_JAAS_CONFIG: sasl.jaas.config=[hidden]

however in 1.4.2.Final and onwards the output has changed due to the parsing errors:

--- Setting property from CONNECT_SASL_JAAS_CONFIG=org.apache.kafka.common.security.scram.ScramLoginModule required username="fakeusername" password: sasl.jaas.config=org.apache.kafka.common.security.scram.scramloginmodule required username="fakeusername" password="fakepassword";

I believe I've traced it back to changes made to the way environment variables are fed into the parser in the entrypoint https://github.com/debezium/docker-images/commit/f25411e5d6061bb40a73dd402a58d2039cc1e71f#diff-2c2a818cf3b7202a01a16e55ab47df3c301f34fea9e16bc57315e22c362fb120R197-R199

I appreciate any help with this issue, I'm not sure if it's a bug or if we've missed some breaking changes with the way we're passing in our environment variables.

Kind Regards,

[Gunnar Morling]

Hi,

I remember some changes to how properties are parsed in the images, there may have an issue slipped in. Can you please report this via a Jira issue?

Thanks,

--Gunnar