Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-7775

Debezium V2.3 & above giving secure connection to SQL Server error for connecto configuration

XMLWordPrintable

    • False
    • None
    • False
    • Important

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      SqlServerConnector (debezium V2.3 and above)

      What is the connector configuration?

      { "connector.class": "io.debezium.connector.sqlserver.SqlServerConnector", "driver.encrypt": "false", "database.user": "User", "database.names": "<DB_Name>", "tasks.max": "1", "database.history.kafka.bootstrap.servers": "<kafkabroker>:9094",  "producer.security.protocol" : "SASL_PLAINTEXT",  "producer.sasl.jaas.config": "org.apache.kafka.common.security.scram.ScramLoginModule required username=\"XXXX\" password=\"XXXXX\";",  "producer.sasl.mechanism" : "SCRAM-SHA-256", "database.history.kafka.topic": "schema-changes.XXXX", "database.server.name": "INST5", "database.port": "<Port_num>", "value.converter.schema.registry.url": "http://sr-devl.XXXX/", "topic.prefix": "server1", "connect.protocol": "eager", "database.hostname": "<DB_Hostname>", "database.password": "XXXXXX", "value.converter.schemas.enable": "true", "value.converter": "io.confluent.connect.avro.AvroConverter", "database.trustServerCertificate": "true", "table.include.list": "dbo.XXXX", "database.include.list": "IgnitionEnterprise", "name": "Connector_name" }

      What is the captured database version and mode of depoyment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      on-premises

       DB version 15.0.4322.2

      What behaviour do you expect?

      Connector should created on Kafka Connect

      What behaviour do you see?

      Getting below error:
      "errors": [
                          "Unable to connect. Check this and other connection properties. Error: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: \"Certificates do not conform to algorithm constraints\". ClientConnectionId:ac069066-779f-4b30-adbb-514dde49c9cf"
                      ],

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      did check with 2.3  & 2.5 are giviing same error. But V1.6 was working fine.

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      No

      How to reproduce the issue using our tutorial deployment?

      Deploy kafka connect with Debezium Image V 2.3 & above , Use above mentioned connector configuration. We are trying to connect Kafka Broker V3.5 (ZK).

       

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      CDC

      Implementation ideas (optional)

      <Your answer>

              Unassigned Unassigned
              gagananandi Gagananandi Chavan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: