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 API Connect
Created by Guest
Created on Dec 2, 2025

API connect support mTLS as a security scheme instead of a checkbox certificate true/false

If we wanted to support mTLS or OAUTH it's not possible with out deploying the API to a mTLS supported gateway and a non-mTLS gateway.  Can the security scheme be changed to have mTLS so that we can support oauth or mTLS.  This should be possible,  as one gateway can support SNIMapping to support mTLS and default non-mTLS traffic as we have today.  When it goes through mTLS, something is flagged for the API.  It checks that certificates were passed:

 

Response body: {"httpCode":"401","httpMessage":"Unauthorized","moreInformation":"Client certificates for application authentication are missing in the API req
uest."}

 

so regardless if I come through mTLS or not, it should be able to check which way I came in.

Idea priority High