Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Created by Guest
Created on Feb 9, 2026

Add native support for HTTP/REST ingestion (POST to Topic) directly within the EEM Gateway with built-in mTLS and Basic Authentication.

Why is it useful? Currently, EEM manages Kafka traffic natively but requires a separate, unmanaged "Kafka Bridge" deployment to handle HTTP producers. This creates two critical gaps for enterprise customers:

  1. The Encryption Gap: The Kafka Bridge does not support TLS on its HTTP listener, forcing customers to run unencrypted traffic inside their cluster or deploy complex Service Meshes.
  2. The Identity Gap: There is no "Credential Mirroring." Customers must manage duplicate secrets (one for the network ingress to validate the user, and one for the Bridge to talk to EEM), breaking the self-service model.

Who would benefit? Financial services and high-security customers (like Banking/Insurance) who require "Zero Trust" (end-to-end encryption) and have 3rd-party partners who require REST/HTTP.

How should it work? The EventGateway component should natively expose an HTTPS listener that accepts POST /topics/{name} requests. It should:

Terminate mTLS directly (using the existing Gateway certs).

Validate the Authorization: Basic header directly against the EEM Identity Manager (just like it validates SASL for Kafka clients).

Eliminate the need for an intermediate proxy (Nginx/DataPower) just to perform protocol translation.

Idea priority High