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 Under review
Categories Event Streams
Created by Guest
Created on Nov 5, 2024

Adding ACL management on the bundled Schema Registry

Hello,

currently the apicur.io schema registry bundled with IBM Event Streams is open for write to all users. This is a potential problem since it allows all users that have access to that schema registry to potentially update schemas that are not their own. 

A typical issue example is an application that is accidentally set with the schema autoload at startup and is delivered with an obsolete/invalid version, that will update a schema and corrupt it for other services working on the impacted topic. 

We would like to have ACLs implemented in the schema registry to ensure that schemas can be created or updated by specific delivery users, and stay read-only for the other.

This update would be of great benefit to entities that require hardening and protection against malignant attempts to corrupt services, such as regulatory and banking services, and in general to any entity that seeks to prevent unwanted issues caused by uncontrolled changes on their platforms.

Thank you for considering this request if you can

Idea priority Medium