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

Pinned ideas

View all
PINNED Add a "Maximum persistent reuse" parameter for the backside of an MPGW or WSP
On an MPGW or a WSP, I want to be able to configure that the persistent backside connection should be closed after X amount of requests have been sent through that connection. I can already do this for the frontside by setting the "Maximum persist...
Share feedback 1
PINNED supports ECDH-ES algorithms for JWE
Debit or credit card tokenizers (THALES / VISA / Etc.) implement JWE with ECDH as an encryption mechanism for sensitive data in the different flows applicable to wallets such as Apple Pay, GPay, etc. given its wide diffusion and easy adoption.
Share feedback 0

All ideas

Showing 2599

CDK: Ability to support multiple HTTP responses and pre-defined outcome examples for the HTTP success response

Each API would have multiple HTTP responses - success and failure. Each successful response could have different scenarios. We need to articulate and help the API consumer handle both the success and failure responses gracefully. The OAS supports ...
about 1 year ago in App Connect 1 Future consideration

CDK: Ability to support multiple pre-defined examples for a query parameter

When clearly defined for the parameters, the examples always help the API consumers in utilising the APIs. When the query parameters are of the type object, the complexity level and onboarding effort increase manyfold. We need to be able to recogn...
about 1 year ago in App Connect 1 Future consideration

CDK: Detail the support for the OAS minor versions

The current import option expects an OAS V2 or V3 document; however, there are significant changes between the v3.0.3 and v3.1 versions of the OAS. We expect the CDK support for the v3.0.3 and the v3.1 specifications to be detailed on the import f...
about 1 year ago in App Connect 1 Future consideration

CDK: Option to perform automated bulk testing

The current process of selecting and testing each API endpoint is quite cumbersome. It works in a PoC kind of setup; however, with a large set of API endpoints and with version updates for the connectors due to breaking changes, it will be impossi...
about 1 year ago in App Connect 1 Future consideration

CDK: Expose the extended log to the Dev user in UI.

While importing the OpenAPI specifications, when the import process encounters an error, it will just throw up and show the developer a generic message "The OpenAPI document you've provided is invalid." It provides a reference number to use while ...
about 1 year ago in App Connect 1 Future consideration

CDK: Improve the version management in the CDK connectors

The process to create and manage the connector versions is quite complex. It over rights the existing connector, is not easy to define and manage and doesn't maintain a history. We would like the capability to be able to create a new version of th...
about 1 year ago in App Connect 1 Future consideration

CDK: Allow configuration of security /authentication options specific to API paths.

Currently, the CDK toolkit will support security / connections options which are globally application for all the APIs. We have a separate set of Login APIs and would like to have specific security options for these APIs and utislie the token gene...
about 1 year ago in App Connect 1 Future consideration

Allow CERT login to MQ Appliance

Allow login to the appliance using Certs.
over 7 years ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

CDK: Ability to define the Global Parameters as an object to support complex structure as per the OAS specification 3.0.3 and 3.1

The Global Parameter configuration is currently missing this option which is preventing us to define the query parameters as complex JSON objects. This prevents us from supporting the advance use cases for the search and data manipulations we have...
about 1 year ago in App Connect 1 Future consideration

CDK : Need an option to configure events in the connector development toolkit to help trigger event driven flows.

The discovery connectors already have this capability. To allow consumers to subscribe to specific events within the source systems and to drive the flow asynchronously; being able to allow a pub-sub method; be able to transmit the same message to...
about 1 year ago in App Connect 1 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.