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
Workspace App Connect
Created by Guest
Created on Oct 8, 2024

Enable SASL/OAUTHBEARER authentication with Kafka nodes

Our security group is strongly discouraging the use of connection strings when we use the Kafka nodes to connect to Azure EventHubs topics.  They are encouraging all uses to switch to OAuth2 (OAUTHBEARER) authentication when connecting to EventHubs.   

Ideally we would be able to pass to the node, using a policy and a credential,  the needed information in order for the flow to obtain a token for connection.  A second option is to allow us to provide a callback handler, packaged as part of the application, were we could write the specific code to obtain the token for the nodes to use.  For this second option, there needs to be a way to obtain the client_id/secret credentials need for the token call. 

Idea priority High