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 Mar 16, 2022

Support of JWKs Endpoint instead of Introspection Endpoint in "Third Party OIDC Provider Config"

Identity providers we currently use often do not offer an introspection endpoint. For this, as it is required by API Connect, we have now offered our own introspection endpoint. This means additional implementation effort and an additional source of errors in the critical auth stack.

A better solution would be:

Ask for the JWKs endpoint as alternative to Introspection Endpoint.

Build the Logic into the third party IDP Service and cache the JWKs for performance.

Then validate using the standards defined by rfc 7519 / 7515

There would be a need to have an option if x5c OR kid should be used to identify the valid public key as auth providers are not consistent in the implementation here.

Thanks for your consideration!

Idea priority High
  • Guest
    Mar 22, 2023

    This capability would be a nice addition, but it should be an addition, not a replacement. It should be possible to select which mechanism will be used, probably at the OAuth provider level (allowing such configuration at the API level could potentially be complex and error prone).