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 API Connect
Created by Guest
Created on May 14, 2020

Catalog support for control of custom host names for API gateways - need v5 flexibiliity in current product version

Issue is with what has changed over time, between what was possible with APIc v5 and what is possible with APIc v2018.

In v5, we had control over how host names were associated with catalogs, and the resulting path to published APIs; it was reasonably easy to get to a host name and API path that did not require we do things like expose the provider org names in URLs.

In v2018, it is much harder to get equivalent configurations defined; to get some specific configuration patterns implemented, the only choices are work-arounds that make TLS handshake management more complex.

Idea priority High
RFE ID 142414
RFE URL
RFE Product IBM API Connect