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 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...

All ideas

Showing 2546

Blacklist and whitelist of email domains

It would be very useful to have some controls in Aspera in order to limit what email addresses users can send to, we have a strict policy for our users not to send client data to non professional email accounts (gmail, outlook etc.)
over 2 years ago in Aspera Ideas 0 Future consideration

Enforce AMS configuration from Client

The aim of Advanced Message Security is to provides a high level of protection for sensitive data flowing through the IBM MQ network. If customer A setup MQ AMS config on the client : SSLKEYR= and keystore.conf This will have the effect that if th...
over 5 years ago in MQ, MQ Advanced & MQ Appliance 2 Future consideration

Remove the 2GB limit for streaming parsers

Streaming parsers (more specifically DFDL in this case) are limited to a file size less than 2 GB for the modeled component of the message, be it the whole file or a parsed record. However using the large message technique with parsing on demand a...
about 10 years ago in App Connect 3 Future consideration

Vulnerabilities Checks done on CP4I

Dear Aha! team, My CSM colleague Wael.Shalaby and I were deploying RedHat Advanced Cluster Security (ACS) on a Cluster that already hosts CP4I, This was done under an initiative we are working on. RedHat ACS revealed the two below security vulne...
over 2 years ago in Cloud Pak for Integration (CP4I) 1 Is a defect

Code/Unit Test Coverage for DataPower services

We would like to determine the code/unit test coverage for a DataPower service(config+XSLT+GWScript) when we execute unit/integration test cases for that particular service. This will help us understand if our test cases are adequate to cover majo...
over 4 years ago in DataPower Gateway 0 Future consideration

Regarding Multiple Sessions in Appliance UI

We need to understand the ability of creating multiple sessions using single user ID in MQ on the application (admin portal) i.e. concurrent logins are not prohibited making application prone to password sharing and chances of distorted audit trai...
over 3 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under 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 for Windows Truststore

We are using Windows 2019 in combination with IBM App Connect.We would like to use the windows Trust store instead of the Java Truststore/Keystore.I know for Java is a parameter: -Djavax.net.ssl.trustStoreType=WINDOWS-ROOT which allows Java to que...
about 1 year ago in App Connect 2 Future consideration

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