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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Given that there is a solution to monitor/investigate tranascation with X-Forward-* headers as explained per above comments, we are closing the request for now. We hope this meets your requirement if not please comment here or open a new Idea. This idea will be kept in IBM's ideas repository and may still be voted on.
In DPOD, you can filter the displayed transactions by the header value that was sent/received as part of the API call. Only available if API-C Analytics data is collected via Payload Capture. So, if you record headers in Analytics and offload this information to DPOD, then you can filter based on any header value, including
X-Forwarded-For.the problem is the real (Source) IP is not reflected in the DataPower logs for the API Gateway service, in the RFE that they're forwarding it to the DataPower team to check this in the context of DPOD but they don't show up in DPOD.
Thank you for opening up this request and this will be switched to the DataPower team for review of the DataPower & DPOD logs.
It should be noted that API Connect does support X-Forward-* headers and these are recorded in our Analytics when the Activity Log Level is set to a minimum of 'header'. We also support the headers as part of the processing flows, for example in the Documentation from our Invoke Policy https://www.ibm.com/docs/en/api-connect/10.0.8?topic=invoke-configuring-policy-datapower-api-gateway
Inject proxy headers
No
If you select this checkbox, the
invokepolicy injects theX-Forwarded-For,X-Forwarded-To,X-Forwarded-Host, andX-Forwarded-Protoheaders to the request that is sent to the target URL.The checkbox is cleared by default.