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.


Status Submitted
Workspace App Connect
Created by Guest
Created on May 26, 2025

Fully implement global proxy support

Because of a bug in V13 we learned that IT45561: ENABLE SUPPORT FOR HTTP PROXY ENV VARS HTTP_PROXY AND HTTPS_PROXY exists. 
While we requesting proxy support in every discovery connector we want to use, which then needs to be implemented and released separately, there is a feature already which almost gives us that functionality for free.

Yet one crucial thing is missing in form of a "noproxy" list of URLs which allows to direct the traffic to the proxy or through internal network based on endpoint URL.

Support told us that, in order to use APAR IT45561, we should create two different integration servers, one with the proxy configuration and one without. Overhead in resource and license consumption aside, this breaks as soon as you want to connect to a SaaS application and an internal application in the same flow.

We don't really understand why putting all the effort in developing dedicated proxy support in every connector, when the product is almost there with a global function.

By the way this would instantly also bring proxy capability to all of the Designer flows.

Idea priority High