Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

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


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Under review
Created by Guest
Created on Apr 23, 2026

Event Endpoint Management Add Prefix / Pattern-Based ACL Authorization along with mtls

We are requesting a scalable authorization model in EEM that supports prefix-based, wildcard-based, or pattern-based ACLs, similar to native Kafka ACL behavior.

Current Behavior

EEM relies primarily on a publish/subscribe object model per alias topic. This creates heavy object sprawl and operational overhead when many topics follow predictable naming patterns.

Problem / Business Impact

This creates a significant scaling problem in enterprise Kafka estates:

  • many applications need access to a family of topics
  • onboarding each topic individually is time-consuming
  • it introduces operational friction and confusion
  • it makes CI/CD and policy-as-code difficult
  • it does not align with common Kafka authorization patterns

Requested Enhancement

Add support for authorization by:

  • topic prefix
  • wildcard
  • regex/pattern
  • direction = consume / produce / both

Example Use Cases

  • payments.*
  • RBKF.COMMOD.*
  • orders.dev.*

Expected Outcome

Administrators should be able to grant access at the topic family/pattern level instead of creating and publishing many individual alias topic objects

Needed By Month