[
https://issues.apache.org/jira/browse/KAFKA-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063196#comment-17063196
]
Sönke Liebau commented on KAFKA-9735:
-------------------------------------
Hi [~SledgeHammer] a common cause for this error is if the private key is
missing from the keystone. Are you using those same keystores for Kafka
communication and are they working there, or are these dedicated to Connect
Rest?
> Kafka Connect REST endpoint doesn't consider keystore/truststore
> ----------------------------------------------------------------
>
> Key: KAFKA-9735
> URL: https://issues.apache.org/jira/browse/KAFKA-9735
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.4.0
> Environment: Windows 10 Pro x64
> Reporter: SledgeHammer
> Priority: Major
>
> Trying to secure the Kafka Connect REST endpoint with SSL fails (no cipher
> suites in common):
> listeners.https.ssl.client.auth=required
> listeners.https.ssl.truststore.location=/progra~1/kafka_2.12-2.4.0/config/kafka.truststore.jks
> listeners.https.ssl.truststore.password=xxx
> listeners.https.ssl.keystore.location=/progra~1/kafka_2.12-2.4.0/config/kafka01.keystore.jks
> listeners.https.ssl.keystore.password=xxx
> listeners.https.ssl.key.password=xxx
> listeners.https.ssl.enabled.protocols=TLSv1.2
>
> See:
> [https://stackoverflow.com/questions/55220602/unable-to-configure-ssl-for-kafka-connect-rest-api]
>
> Developer debugged and saw the configs are not being returned. I am still
> seeing this issue in 2.4.0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
