Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace API Connect
Created by Guest
Created on Dec 12, 2023

API Connect-managed DataPower user agent 'webapi' should be configurable via OpenShift ConfigMap

The user agent 'webapi' used by API Connect-managed API Gateway service on DataPower should allow proxy settings to be configurable using an OpenShift ConfigMap applied to the relevant CP4I Enterpirse Gateway apiconnect application domain configuration.

This has been in a production API Connect v5 environment for years, but is not configurable on v10 in CP4I / OpenShift.

Example DataPower configuration "webapi-user-agent-proxy.cfg" for creating ConfigMap:

user-agent webapi
proxy "*" "proxy.server.local" "8080"

ConfigMap is either created or updated with, respectively:
`oc create configmap webapi-user-agent-proxy --from-file=webapi-user-agent-proxy.cfg -n cp4i-api-gateway`
`oc set data configmap/webapi-user-agent-proxy –from-file=webapi-user-agent-proxy.cfg -n cp4i-api-gateway`

The result is the proxy settings are not applied to the 'webapi' user agent.

HOWEVER, it works if this is done using just a config for the default user agent:

proxy "*" "proxy.server.local" "8080"

It should work regardless of the named user agent.

Idea priority High