Bo Gao created KAFKA-15053:
------------------------------
Summary: Regression for security.protocol validation starting from
3.3.0
Key: KAFKA-15053
URL: https://issues.apache.org/jira/browse/KAFKA-15053
Project: Kafka
Issue Type: Bug
Components: clients
Affects Versions: 3.3.0
Reporter: Bo Gao
This Jira issue introduced validations on multiple configs. As a consequence,
config {{security.protocol}} now only allows upper case values such as
PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL. Before this change, lower case values
like sasl_ssl, ssl are also supported, there's even a case insensitive logic
inside
[SecurityProtocol|https://github.com/apache/kafka/blob/146a6976aed0d9f90c70b6f21dca8b887cc34e71/clients/src/main/java/org/apache/kafka/common/security/auth/SecurityProtocol.java#L70-L73]
to handle the lower case values.
I think we should treat this as a regression bug since we don't support lower
case values anymore since 3.3.0. For versions later than 3.3.0, we are getting
error like this when using lower case value sasl_ssl
{{Invalid value sasl_ssl for configuration security.protocol: String must be
one of: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
