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

All ideas

Showing 2614

MQ .NET Managed Client: Support alias CipherSpecs such as ANY_TLS13_OR_HIGHER

In MQ .NET Managed Client, please add support for alias CipherSpecs such as ANY_TLS13_OR_HIGHER. A queue manager provider supports several cipher specs and recommends we configure the alias CipherSpec rather than a specific cipher, however, MQ .NE...
about 1 year ago in MQ, MQ Advanced & MQ Appliance 1 Future consideration

API Connect: Add support for custom parameters in product plans

Currently, only the transaction rate can be set up in an API product plan. We have a use case where a consumer is allowed to submit attachments up to a certain size, based on a subscribed (and approved) plan. Since there is no way to do this today...
over 4 years ago in API Connect 0 Future consideration

Resubmitting backed-out messages

BOQNAME and BOTHRESH attributes of a local queue are incomplete solution to the problem discussed as early as for example this: http://www.mqseries.net/phpBB2/viewtopic.php?t=24679Add further BO attribute(s) to the queue that will control qmgr beh...
about 6 years ago in MQ, MQ Advanced & MQ Appliance 4 Not under consideration

[Orchestrator] Respect permissions for API

Appears that to be able to run next api calls the user needs to have Aspera:Orchestrator:Monitor permissions: ${orcUrl}/aspera/orchestrator/api/work_orders_list/${workflow_id}?format=json&status=${status}&max_results=${maxResults}&from...
7 months ago in Aspera Ideas 0 Under review

New encription method to use with Kerberos client keytabs in communication with modern Windows Servers

If You need to start secured communication from DP GW (or ACE) to modern Windows Servers normally You could use Kerberos client keytabs. After recent changes in Kerberos / Netbios protocols Microsoft "say goodby" to last availble encription method...
about 1 year ago in DataPower Gateway 1 Functionality already exists

RDQM: Protection of the data in transit

Good day, IBM MQ Advance 9.2.0.x does not support protection of the data in transit during data replication in between nodes when using RDQM DR/HA solution, like TLS encryption.This means that banks are unable to use it in the default form, becaus...
almost 4 years ago in MQ, MQ Advanced & MQ Appliance 1 Not under consideration

SAP Adapter Discovery Agent Wizard should provide valid Message Model for Function Modules / BAPIs

BAPI "import" parameters and "export" parameters are separated from one another within SAP e.g. see SAP transaction SE37 (two tabs / separate views): This allows import parameters to be defined as mandatory / optional independent of any export par...
over 3 years ago in App Connect 2 Future consideration

IBM Software Install Dates

While working with IBM License Metric Tool (ILMT), we encountered one of the possible modifications critical to Software Asset Management and that is the inclusion of IBM Software Install Dates. ILMT does not provide installation dates at the mome...
7 months ago in IBM License Metric Tool (ILMT) 2 Not under consideration

Microsoft Azure Blob storage Request Node should support container level SAS token authentication

Microsoft Azure Blob storage Request Node should support container level SAS token authentication. Currently it supports authentication using tenant Id or Access Keys at storage account level, however in real world implementation, customers are no...
over 1 year ago in App Connect 2 Future consideration

A DataPower service using kerberos authentication in AAA policy is producing huge log every day.

The service uses Kerberos authentication in AAA policy. Every first transaction of the Kerberos authentication process/steps in that service is failing with “AAA Authentication Failure” error and responds with HTTP 401 to the client. This is happe...
over 4 years ago in DataPower Gateway 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.