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 Feb 10, 2021

API Connect Financial-grade API compliant

In the banking customer, Financial-grade API (FAPI) compliant is requested.
API Connect have some capability for FAPI specification, but it is not full.
OpenID FAPI certification is required.

Idea priority Medium
RFE ID 148527
RFE Product IBM API Connect
  • Guest
    Nov 26, 2021

    We (CosmosDirekt) as an german insurance company and user of the API Connect product strongly support this feature request. We have the requirement to secure our APIs as good as possible, since we are processing personal and confidential data.

    From our point of view the currently supported OAuth flows supported by the product (especially OAuth Client Credentials Flow with clientID and secret) are not sufficient to cover our regulatory requirements. From our point of view we would like to implement OAuth Client Credentials Flow with private-key-jwt. As you see in the FAPI standard this is also part of the AdvancedSecurity Profile - so this gives us the opportunity to adequately secure high-risk APIs. Even if the product does not fully support all client authentication methods described in the FAPI standard, at least the private_key_jwt support would be a very important asset. Thanks for taking that into consideration!

    Regards, Thomas Matal