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 Not under consideration
Workspace webMethods API Gateway
Created by Guest
Created on Nov 3, 2025

RELATED IDEAS

Client IP Spoofing Issue

We noticed that the extended setting 'watt.server.enterprisegateway.ignoreXForwardedForHeader' in wm.io API Gateway was defaulted to false, although the documentation states the default is true.

We however changed this to true, and tried to pass custom IP address against header property 'X-Forwarded-For' from Postman project. As per this extended setting being true, this client IP address should not have got picked up as part of the API fault error message. However we could still see the IP address as passed in the header.

 

When we raised this query with IBM support, we were advised that the above extended setting is applicable only for Integration Server and not for API Gateway. However it is strange that this Extended setting is still visible in API Gateway on wm.io and if not relevant for API Gateway, it should not be available. 

 

We were also told that currently this is an expected behaviour where the client IP address supplied in header of the API request (could be used for IP spoofing), is expected to be picked up and used as the actual client IP addresss. This is a security flaw and has already been raised as security issue as part of the Pen Testing.

 

We request a fix for this issue, either in the form of fix or the extended setting working for API Gateway as well.

Idea priority Low
  • Admin
    Sivaraj Lenin
    Nov 6, 2025

    Thank you for your suggestion. The behavior arises from differences between threat protection and API-level Identify/Authorize policies. IAM policies should be used to identify consumers via addresses only when the trusted load balancer at the boundary is configured to overwrite the X-Forwarded-For header. We do not plan changes in this area and appreciate your continued support.

    Reply

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.