Skip to Main Content
Integration
Hide about this portal


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.


Disable access to the API when OAuth 2.0 authentication mode is enabled, Two-way SSL Security Mode is set to exclusive, and the user call's the API directly on port 443 without presenting a valid certificate

See this idea on ideas.ibm.com

We aim to enhance the security of our APIs exposed through the Apigee gateway and developed in webMethods Integration by implementing mTLS between Apigee and webMethods. However a challenge arises: when the authentication mode is set to OAuth 2.0, it’s still possible to access these APIs on port 443 without presenting a certificate.

Idea priority High
  • Admin
    John Carter
    Reply
    |
    Mar 31, 2025

    In the future we will be removing basic auth from the platform, before that we will make it an optional feature as oposed to the current mandatory option, but unfortunately today you cannot disable it. Sorry.

    From your last comment I see that you would like to also block all ingresses based on a single/set of client certificates, and again as part of the work to make basic auth optional we will introduce the concept of client services that will define the authentication type. You will then decide which resources will be given access to client service.

  • Guest
    Reply
    |
    Mar 31, 2025

    Currently, the APIs exposed on our IPaaS are secured using OAuth2 authentication, as shown in the attached screenshot. However, Basic Authentication is still enabled, allowing access via this less secure method.

    We would like to disable Basic Authentication on these APIs, keeping OAuth2 as the only authentication method to strengthen security.

    Additionally, we aim to enhance security by implementing mTLS between Apigee gateway and IPaaS. This setup would ensure that the APIs are accessible exclusively via Apigee by requiring a valid client certificate for verification on port 8443.

    Could you please confirm if this configuration is possible and provide any relevant guidance?

  • Admin
    John Carter
    Reply
    |
    Mar 31, 2025

    I don't understand your request here. Currently there is no way to set the authentication mode for an API in Integration. It's either basic auth or private, so can you explain your current process in more detail please.