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

All ideas

Showing 3342 of 3342

Allow API endpoint aspera/faspex/api/v5/packages and others to accept case insensitive email address

Currently calls to the /faspex/api/v5/packages endpoint will generate an error of " This package failed validation - Invalid recipient: "SOmeemailAddress@example.com" if case isn't exactly matched for local accounts. This is problematic from a usa...
over 1 year ago in Aspera Ideas 0 Under review

TLS information logged to log target

We need to be able to track what version of TLS is used and with what cipher suite. The support case indicate that the tls-info variable currently causes stability issues, but honestly even if it did not we have to much code to add this every wher...
about 5 years ago in DataPower Gateway 0 Future consideration

Parameter to change pub.client:smtp `transportLayerSecurity` value globally

Having several invocations of pub.client:smtp will require high maintenance when there is a change in transportLayerSecurity (i.e from `explicit` to `implicit`. A parameter to change it globally would avoid that implication
over 1 year ago in webMethods Integration/Microservices Runtime 1 Future consideration

multi-factor authentication (MFA)

Multi-factor authentication (MFA) is must have requirement in today's remote working model to securely validate user identity. Allowing AHST/Aspera Share UN/PW authentication doesn't seems to be an adequate security.
over 4 years ago in Aspera Ideas 5 Functionality already exists

mqsicreatebar command with '-JDKCompilerVersion 8'

mqsicreatebar -data C:\Users\ddomagalskidev\Desktop\ace\sii-integration-ace\sii-integration-ace -b C:\Users\ddomagalskidev\Desktop\ace.bar -a AdapterAD -deployAsSource -trace -v /tmp/createbar.log -skipWSErrorCheck -JDKCompilerVersion 8 INFO: Regi...
8 months ago in App Connect 0 Submitted

Disable access to the API when OAuth 2.0 authentication mode is enabled, Two-way SSL Security Mode is set to exclusive, and the user call's the API directly on port 443 without presenting a valid certificate

We aim to enhance the security of our APIs exposed through the Apigee gateway and developed in webMethods Integration by implementing mTLS between Apigee and webMethods. However a challenge arises: when the authentication mode is set to OAuth 2.0,...
8 months ago in webMethods Integration SaaS 4 Planned for future release

Websphere MQ - enhance CHLAUTH User mapping with wildcards

Enhance MQ v7.5 and v8 to provide a more flexible CHLAUTH feature for the USERMAP feature. Currently this allows mapping of a "client asserted" id to another id value for MCAUSER purposes. However it does not allow wildcards in the client id mappi...
over 11 years ago in MQ, MQ Advanced & MQ Appliance 4 Future consideration

recursive ldap-search / ldap-search filter should support all RFC 2254 specification [including extensible Match]

The following ldap-search filter needs to be processed by DataPower: (&(memberOf:1.2.840.113556.1.4.1941:=CN=someGroup,OU=MyOU,OU=Gruppen,DC=uv,DC=xyz,DC=de)(objectCategory=person)(objectClass=user)) This is a extensible Match and works on LDA...
about 7 years ago in DataPower Gateway 0 Not under consideration

Produce the QESD and QEST records each interval

IBM MQ for z/OS produces inconsistent SMF records, which can cause misinterpretation of the data used to evaluate the CF structures and the SMDS information.
over 4 years ago in MQ, MQ Advanced & MQ Appliance 2 Is a defect

Add ability to Error Catch logic be added for Batch Flows in Designer Flows

In designer flows without a batch flow it is possible to add an Error Catch to the flow and within that error catch perform specific error handlng based on the information found in the Error Details object. In flow with a batch flow included, the ...
almost 2 years ago in App Connect 2 Future consideration