[
https://issues.apache.org/jira/browse/KAFKA-15053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736529#comment-17736529
]
Chris Egerton edited comment on KAFKA-15053 at 6/23/23 3:31 PM:
----------------------------------------------------------------
[~dlgaobo] I think that may have been a typo, but just to be extra clear–we
will never backport this to 3.3.0, which has already been released. We may
backport it to the 3.3 branch, which will then cause the change to be included
if we do another 3.3.x release (right now, that would be 3.3.3).
Assuming you're asking about 3.3.x in general and not 3.3.0 specifically, then
yes, I believe that once they've upgraded to the new version (e.g., 3.3.3),
there's nothing else users will have to do to benefit from this fix. However,
again, I'm not certain there will be another 3.3.x release, so they may have to
upgrade to a 3.4.x version to get this fix.
was (Author: chrisegerton):
[~dlgaobo] I think that may have been a typo, but just to be extra clear–we
will never backport this to 3.3.0, which has already been released. We may
backport it to the 3.3 branch, which will then cause the change to be included
if we do another 3.3.x release (right now, that would be 3.3.3).
Assuming you're asking about 3.3.x in general and not 3.3.0 specifically, then
yes, I believe that once they've upgraded to the new version (e.g., 3.3.3),
there's nothing else users will have to do to benefit from this fix. However,
again, I'm not certain there will be another 3.3.x release, so they may have to
upgrade to a 3.4.x version to benefit from this fix.
> 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
> Assignee: Bo Gao
> Priority: Major
>
> [This|https://issues.apache.org/jira/browse/KAFKA-13793] 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)
