# connect solace to kafka (not confluent)

**URL:** <https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241>\
**Category:** Connectors & Integrations\
**Created:** [April 6, 2020, 7:28pm UTC](https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241 "2020-04-06T19:28:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eddie](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@eddie](https://community.solace.com/u/eddie)\
**Post date:** [April 6, 2020, 7:28pm UTC](https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241/1 "2020-04-06T19:28:54Z")

</div>

Hi,  
I got solace pub/sub running locally. I can publish to a queue under a topic and consume from it via a subscription. I also have kafka/zookeeper running under WSL. I am trying to connect solace to standalone kafka by following Heinz Schaffner’s video: [Integration Guides](https://docs.solace.com/Developer-Tools/Integration-Guides/Kafka-Connect.htm) using the Solace source connector.

> sudo bin/connect-standalone.sh config/connect-standalone.properties solace.properties  
> returns this error: Failed to connect to and describe Kafka cluster. Check worker’s broker connection and security properties.  
> I am not sure if I had considered solace.properties correctly. I took the one downloaded from Heinz and replaced the sol.host/sol.username/sol.password/sol.vpn/sol.topic with my own and left everything else alone including all the sol.ssl fields. There may be other things I missed too.  
> Any help will be appreciated.  
> Eddie

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/solace/original/1X/1248f38eea018157e66cc024e8284f3331a54f94.png) [@system](https://community.solace.com/u/system)\
**Post date:** [April 7, 2020, 3:07pm UTC](https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241/2 "2020-04-07T15:07:12Z")

</div>

Eddie:  
The first thing a Connector checks is the Kafka access. As you reported this failed, so it never gets to try the Solace connection. The error you received usually is a result of failing to authenticate to the Broker. Have you enabled any authentication or secure transport for your Kafka Brokers? If so, then the connect-standalone.properties file must be updated to reflect the security requirements from the Connect Cluster.  
Heinz

---

<div class="post-metadata">

**Author:** ![eddie](https://avatars.discourse-cdn.com/v4/letter/e/f07891/32.png) [@eddie](https://community.solace.com/u/eddie)\
**Post date:** [April 8, 2020, 1:51pm UTC](https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241/3 "2020-04-08T13:51:15Z")

</div>

Heinz,  
Thank you so much for responding. I got yanked away to do something else. Will get back to this when I have a chance.  
Eddie

---

<div class="post-metadata">

**Author:** ![Aaron](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/aaron/32/843_2.png) [@Aaron](https://community.solace.com/u/Aaron)\
**Post date:** [April 29, 2020, 7:38am UTC](https://community.solace.com/t/connect-solace-to-kafka-not-confluent/241/4 "2020-04-29T07:38:24Z")

</div>

Hey @eddie … any update here? Would be good to know if you got this working.