[ https://issues.apache.org/jira/browse/KAFKA-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-13964. ------------------------------------- Resolution: Duplicate Thanks for reporting the issue. This will be resolved by https://issues.apache.org/jira/browse/KAFKA-14084. > kafka-configs.sh end with UnsupportedVersionException when describing TLS > user with quotas > ------------------------------------------------------------------------------------------- > > Key: KAFKA-13964 > URL: https://issues.apache.org/jira/browse/KAFKA-13964 > Project: Kafka > Issue Type: Bug > Components: admin, kraft > Affects Versions: 3.2.0 > Environment: Kafka 3.2.0 running on OpenShift 4.10 in KRaft mode > managed by Strimzi > Reporter: Jakub Stejskal > Priority: Minor > > {color:#424242}Usage of {color:#424242}kafka-configs.sh end with > {color:#424242}org.apache.kafka.common.errors.UnsupportedVersionException: > The broker does not support DESCRIBE_USER_SCRAM_CREDENTIALS when describing > TLS user with quotas enabled. {color}{color}{color} > > {code:java} > bin/kafka-configs.sh --bootstrap-server localhost:9092 --describe --user > CN=encrypted-arnost` got status code 1 and stderr: ------ Error while > executing config command with args '--bootstrap-server localhost:9092 > --describe --user CN=encrypted-arnost' > java.util.concurrent.ExecutionException: > org.apache.kafka.common.errors.UnsupportedVersionException: The broker does > not support DESCRIBE_USER_SCRAM_CREDENTIALS{code} > STDOUT contains all necessary data, but the script itself ends with return > code 1 and the error above. Scram-sha has not been configured anywhere in > that case (not supported by KRaft). This might be fixed by adding support for > scram-sha in the next version (not reproducible without KRaft enabled). > -- This message was sent by Atlassian Jira (v8.20.10#820010)