[
https://issues.apache.org/jira/browse/SOLR-18411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113361#comment-18113361
]
ASF subversion and git services commented on SOLR-18411:
--------------------------------------------------------
Commit 5aca7607cbdf5df72edb71b04d331ca41cdffd75 in solr's branch
refs/heads/branch_10x from Andrzej Bialecki
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5aca7607cbd ]
SOLR-18411: CrossDC: Configure security properties in KafkaMirroringSink
initConsumer. (#4883)
(cherry picked from commit c43a9a56d199f9405bb0404822ddfd7c1391a936)
> CrossDC Producer: KafkaProducerSink's KafkaConsumer gets no security config
> ---------------------------------------------------------------------------
>
> Key: SOLR-18411
> URL: https://issues.apache.org/jira/browse/SOLR-18411
> Project: Solr
> Issue Type: Bug
> Components: module - crossDC
> Affects Versions: 10.0, 9.10.1
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Labels: pull-request-available
> Fix For: main(11.0), 10.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Unlike the initialization in {{KafkaCrossDcConsumer}} constructor, the
> instance of {{KafkaConsumer}} created in {{KafkaMirroringSink}} is created
> with a configuration that doesn't get Kafka-related security properties -
> it's missing a call to {{{}KafkaCrossDcConf.addSecurityProps{}}}.
> This means that every declared {{SECURITY_CONFIG_PROPERTY}} (including
> {{security.protocol}} and all {{ssl.*)}} is silently dropped from the
> {{KafkaConsumer}} the sink builds for its topic-availability check. On a
> secured cluster that client cannot connect, and the failure surfaces as an
> unrelated topic-availability error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
