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

Pinned ideas

View all
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.
PINNED Request for Adding Limited GitOps Functionality to default Domain
We have some use cases around form factor portability and cloud instance provisioning where it might be helpful to have an automated approach to loading common configurations to the default domain through GitOps. Some examples are the RBM and ODR ...

All ideas

Showing 3209

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 2 years ago in App Connect 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 2 years 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 2 years ago in App Connect 1 Future consideration

Option for Aspera Async API to allow changing of the destination host.

When attempting to update an async job created through APIs to change the destination server, it will always generate the following error code: "error: code 400 reason bad request user message: configuration.local.path, configuration.remote.host a...
about 2 years ago in Aspera Ideas 0 Future consideration

Make Connect sync jobs visible in the Aspera Console

By design this is not supported (ATS - console - connect-async), you won't be able to see it in the Aspera console.
about 2 years ago in Aspera Ideas 2 Future consideration

Add explanation and action to errors in output of DiagnosticsMessages stanza (JSON format)

In the traditional diagnostics logs (often referred to as error-logs) there is an explanation of each error and suggested actions to solve the issue. From MQ v9 onwards it is also possible to have additional log stanzas; one of those is the Diagno...
about 4 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

MQ Error logs written to queue

Currently the queue manager error logs have extension .LOG and .JSON. On distributed environment, number of queue managers grow and managing each host/vm eror log is difficult. Similar for appliance, download the logs frequently. This allows easy ...
about 4 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

HTTP Reply Nodes fail to recognise duplicate replies (SOAP Reply nodes do detect this)

When a HTTP timeout occurs using a broker-wide listener, the processing thread continues to process resulting in an attempt to submit a duplicate HTTP response message. When using SOAP Nodes, this duplicate response attempt results in an exception...
over 10 years ago in App Connect 2 Future consideration

Ignore RFH2/mcd folder on MQInput node

On the MQInput node the mcd foldder in MQRFH2 header takes presecence over the parser settings on the node. It should be possible to ignore the mcd folder so the configured parser is always used (parser option ingnore mcd).
over 8 years ago in App Connect 2 Future consideration

APIC dynamic scope

In order to be compliant with Open Banking/PSD2 regulation, oauth need to support rich authorization data in conformance with RFC 6749. Open Banking/PSD2 proposes Lodging Intent Pattern(An extensive description can be found at the OpenID Foundatio...
about 2 years ago in API Connect 0 Future consideration