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 May 8, 2019

TLS Profile changes require downtime

We have a cluster of 2 gateway servers for Gateway service that are balanced by external LB F5. Also for all inbound calls to API's, we implemented 2-way SSL by checking the validate client certificate and import the partners certificate in to trust store.
As the products are offered to various clients, we need to import the client certs in to TLS profile that is associated to production catalogs gateway. In order to do it, we are forced to remove the servers and modify the TLS profile and re-add the same and deploy the custom script files and other custom log targets in to the APIM domain associated to that environment. It is leading to considerable production environment downtime to facilitate all this.

All this causing issues in addressing our commitment to our partners for service offerings where SLAs are defined as 24X7 365 days.

Found verbiage in regard to it at the following URL:

Look out for the verbiage “To be able to change a TLS Profile for a DataPower Service in the CMC, all servers must first be deleted from the Service.”

We need an alternative solution or patch to address these concerns at the earliest.

Please do the needful ASAP

Idea priority Urgent
RFE ID 132750
RFE Product IBM API Connect