Skip to Main Content
IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Under review
Created by Guest
Created on Apr 27, 2022

Configure multiple certificates for the Replication Engine

The Replication Engine for Kafka currently uses a single keystore for the certificates used to encrypt both the connection to its source datastore and the connection to the targeted Schema Registry.


Although it is possible to configure multiple certificates within the keystore, only the certificate with the alphabetically first alias is chosen for encryption.


However, our security guidelines require us to use a certificate of the network hostname for encrypting the connection between Replication Engine and source datastore and a certificate of the user for writing to the Schema Registry. Both hostname and user name cannot be the same, requiring us to use two different certificates. This cannot currently be configured and prevents us from running CDC in our production environment.


A possible solution would be to either allow configuring two different keystores or to configure the alias names of any certificates to use for either connection.

Needed By Month
  • Guest
    May 10, 2022

    Looking further into this issue, the keystore should be configurable by creating a KCOP and setting the variables

    schema.registry.ssl.keystore.location

    schema.registry.ssl.keystore.password

    schema.registry.ssl.key.password

    schema.registry.ssl.truststore.location

    schema.registry.ssl.truststore.password

    to the configuration map passed to the KafkaAvroSerializer. These parameters are (at least in the Confluent implementation which I understand CDC to use) eventually passed to SslFactory to create parameters for an SSL connection. I do not understand why setting these parameters does seem to have any effect at all.