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 OpenAPI schema validation including headers
Currently to schema validate a REST based API in DataPower you have to extract the JSON schema from the OpenAPI file and then code manually code the individual header checks defined in the OpenAPI file Would be a vast improvement to be able to j...
Share feedback 1

All ideas

Showing 3327 of 3327

Provide option to use token based auth (Oauth/JWT) for JMS messaging

Currently, we can only use basic authentication mechanism to connect to JMS systemes using messaing in webmethods integration server. We are facing difficulty from our internal security architecture teams to get approval to use basic auth to conne...
5 months ago in webMethods Integration/Microservices Runtime 1 Submitted

Assess and modify Cloud Pak for Integration to adhere to Kubernetes Application security controls and best practices for hardening applications to benefit Ford, IBM, and other IBM customers

To improve the availability, reliability, security, and scalable operations of Ford’s OpenShift clusters and the applications that share them, Ford Motor Company is enforcing K8s policies and best practices from Red Hat, Google, the Cloud Native C...
5 months ago in Cloud Pak for Integration (CP4I) 3

MQ Support for Distributed Tracing

Existing Application Performance Management (APM) tools, and emerging W3C standards for Distributed Tracing require propagation of tracking meta data across application protocols. For applications using HTTP as the communication protocol between a...
over 5 years ago in MQ, MQ Advanced & MQ Appliance 3 Not under consideration

AoC: Client Access Keys with Custom Rights per key

When making a Client access key in Applications>Files>Shared Folders>(share)>Client Access Keys, there is no setting for changing the rights to that key. You can change the rights for users within Aspera on Cloud, but not for the share...
over 1 year ago in Aspera Ideas 1 Under review

Rate-limiting configuration for specific APIs

Hello everyone, Actually, it is possible to configure a rate-limiting but it is applied for the whole GTW and thus all the APIs are impacted. Rate-limiting is a great security protection to add in APIs but each project has its needs. Indeed, one r...
5 months ago in webMethods API Gateway 3 Functionality already exists

More flexible use of Security Profiles - pulling credentials into flows at runtime

Pulling credentials in at runtime, from those set against a Security Profile, would enable more creative use of the credentials. Currently Security Profiles can only be used in a limited capacity e.g. to propagate credentials for use with HTTP Bas...
about 1 year ago in App Connect 3 Future consideration

Add cache for POST method request (service result cache)

Hello everyone, I am Béatrice HUYNH I am in the API team from Mobilize. When we have a project where we have to retrieve a token through a POST method, after to cache the token value obtained (with service result cache) in order to authenticate to...
5 months ago in webMethods API Gateway 2 Not under consideration

LDAP Group mapping for consumer organizations

Since version 10.0.2 the ldap group mapping for pOrg and the CMC was introduced. We also think it is beneifical to be able to map ldap group to roles in a consumer organisation. Currently this is not supported.
almost 3 years ago in API Connect 2 Future consideration

Admin GUI Search Functionality within packages

Hardcoded values within FlowServices are hard to track, hence some kind of report is required to show these values to an Administrator within Admin GUI. We want to check a specific hardcoded value at the server level or at least package level. Or ...
10 months ago in webMethods Integration/Microservices Runtime 0 Not under consideration

MQ WEB UI to display Cluster queues when an Alias queue is filtered

As organizations use MQ CLuster; there are a lot of Alias queue routing to a single/multiple cluster local queues. Web UI should provide list of Cluster Local queue for the corresponding alias queue. Example: QALIAS on QM1 > DEFINE QA(A1) TARGE...
over 3 years ago in MQ, MQ Advanced & MQ Appliance 0 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.