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 Subscribe
Status Future consideration
Workspace API Connect
Created by Guest
Created on Aug 3, 2020

RELATED IDEAS

Fix TLS MITM attack vulnerability

The datapower gateway (that acts as a client in a TLS handshake) does not check if the domain name of the endpoint URL can be matched against the CN or the SAN in the certificate (despite the TLS profile we configure explicitly states to do that). So this connection does not comply to https://tools.ietf.org/html/rfc2818#section-3.1.

So the gateway doesn't know for sure it is talking to the correct endpoint server. It can also be a Man In The Middle with a valid, signed certificate but with another name.

As a solution IBM suggests to store the server certificate in the Truststore but that is only a workaround for servers from which you can receive renewed certificates BEFORE they are renewed at that server. That is not always the case. In addition this workaround introduces extra manual actions with extra risks for availability of the system.

See also case TS003941197.

Idea priority Urgent
RFE ID 144372
RFE URL
RFE Product IBM API Connect

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.