[
https://issues.apache.org/jira/browse/KAFKA-13859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529293#comment-17529293
]
Luke Chen edited comment on KAFKA-13859 at 4/28/22 8:18 AM:
------------------------------------------------------------
[~dengziming] , Nice finding!
[~opayne] , thanks for reporting. Could you share more info to us? Like the
error call stack? Or even better, complete client or broker logs or partial
logs during the error happening. We're still unsure if [~dengziming] 's finding
is the root cause of your issue, or is there any other places having the same
issue. Please help.
Thank you!
was (Author: showuon):
[~dengziming] , Nice finding!
[~opayne] , thanks for reporting. Could you share more info to us? Like the
error call stack? Or even better, complete client or broker logs or partial
logs during the error happening.
Thank you!
> SCRAM authentication issues with kafka-clients 3.0.1
> ----------------------------------------------------
>
> Key: KAFKA-13859
> URL: https://issues.apache.org/jira/browse/KAFKA-13859
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 3.0.1
> Reporter: Oliver Payne
> Assignee: dengziming
> Priority: Major
>
> When attempting to produce records to Kafka using a client configured with
> SCRAM authentication, the authentication is being rejected, and the following
> exception is thrown:
> {{org.apache.kafka.common.errors.ClusterAuthorizationException: Cluster
> authorization failed.}}
> I am seeing this happen with a Springboot service that was recently upgraded
> to 2.6.5. After looking into this, I learned that Springboot moved to
> kafka-clients 3.0.1 from 3.0.0 in that version. And sure enough, downgrading
> to kafka-clients resolved the issue, with no changes made to the configs.
> I have also attempted to connect to a separate server with kafka-clients
> 3.0.1, using plaintext authentication. That works fine. So the issue appears
> to be with SCRAM authentication.
> I will note that I am attempting to connect to an AWS MSK instance. We use
> SCRAM-SHA-512 as our sasl mechanism, using the basic {{ScramLoginModule.}}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
