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.


ADD A NEW IDEA

API Connect

Showing 208

Support for parameter validation based on OASv3 Spec

As described in https://swagger.io/specification an API specification can define parameters where each parameter can be defined by a schema object. With the help of the schema object an API developer can define validation rules for parameters. The...
over 3 years ago in API Connect 2 Future consideration

Support for client_secret_jwt in OAuth Provider Implementation.

In the banking and insuarance customer, Financial-grade API (FAPI) compliant is requested.In particular, our customer(insuarance) are requesting the implementation of a more secure authentication method: client_secret_jwt. https://openid.net/specs...
about 1 year ago in API Connect 0 Future consideration

Support to turn off Transfer-Encoding chunked and pass Content-Length to HTTP 1.1 or later protocols

Our backend service endpoints support HTTP 1.1 and HTTP 1.2 protocols. But they only work with Content-Length and not Transfer-Encoding chunked in the header. Hence we're unable to use the Invoke function provided by the tool since its introductio...
over 4 years ago in API Connect 0 Future consideration

Possibility to onboard users with different user registries including the ability to have a Sign-up page that defaults to the correct one dependent on audience.

Due to that we today use three different user registries depending on type of user we would like to be able to invite users in Developer’s Portal to the correct user registry. The three types of users we have identified so far are Administrators, ...
over 3 years ago in API Connect 0 Future consideration

Set Default View for API Explorer Developer Portal

When an end user log in in the dev portal, the used user registry should be stored in the local cache. Then select this user registry automatically when the end user opens the “sign in” page the next time. Moved APICONN-I-582 In the same way, stor...
over 3 years ago in API Connect 0 Future consideration

Dynamic TLS Client Profile in Invoke Policy

Currently, we have a requirement to use TLS client profiles dynamically depending on the incoming request. The invoke policy's TLS profile setting is a drop-down that only allows the selection of known TLS profiles. The invoke policy should suppor...
about 1 year ago in API Connect 1 Future consideration

User registries should not require unique email IDs

Today API Connect has the following restrictions/requirements regarding user registries: All users of the following kind must be registered with an email ID: users in local user registries consumer users (local or non-local user registries) In any...
over 3 years ago in API Connect 0 Future consideration

Support multiple "Custom Pattern" headers for OAuth providers

The OAuth Provider configuration should allow for multiple headers to be passed through to the backend. Currently it allows for a single "Custom Pattern" to be defined. It would be better to allow a developer to either define multiple custom patte...
almost 5 years ago in API Connect 0 Future consideration

API Connect - Activity Log Control and Detection

We would like to have the possibility of switching off / disabling the activity log option in an Organization / catalog level . We know its possible to switch off in API level , but it is beneficial to have the option of disabling payload option i...
over 3 years ago in API Connect 0 Future consideration

Offer a feature in the AMU to allow archive:push by Space

Currently, the AMU cannot filter pushed artifacts by Space. The lowest you can filter is Catalog. We have 20+ spaces and workarounds to push 1 Space at a time is time-consuming and error-prone.
over 2 years ago in API Connect 0 Future consideration