[KAFKA-15053] Regression for security.protocol validation starting from 3.3.0

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.3, 3.6.0, 3.5.1, 3.4.2
• Component/s: clients
• Labels: backport
• Assignee: Bo Gao
• Reporter: Bo Gao
• Reviewer: Divij Vaidya
• Created: 02/Jun/23 23:31
• Updated: 29/Jun/23 17:24
• Resolved: 29/Jun/23 17:17

Description

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 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

Issue Links

• links to: GitHub Pull Request #13831