Using solace sink connector in MSK environment

Hi, I am trying to use solace sink connector - Solace Sink Connector for Confluent Platform | Confluent Documentation

However, if I tried with all options ( PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL ) of confluent.topic.security.protocol, I am not able to get the connector started, if the MSK bootstrap server is not compatible with confluent solace sink connector?

This is indeed a Confluent commercial connector and does require a license as well as being on a Confluent Server cluster as a backing cluster for the connect workers . See: Solace Sink Connector for Confluent Platform | Confluent Documentation

1 Like

I cannot even try that under MSK environment?

There is a 30 day trial you can use, but @sarwarbhuiyan’s point is that even if you like it you wouldn’t (IIUC) be able to licence it for use with MSK.

To your question though - can you share further details of the problem. What error are you getting with each configuration that you try?

1 Like

thanks, I keep getting this exception:

Caused by: org.apache.kafka.common.KafkaException: Principal could not be determined from Subject, this may be a transient failure due to Kerberos re-login