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.


Add a new idea Subscribe
Status Submitted
Workspace API Connect
Created by Guest
Created on Dec 5, 2024

RELATED IDEAS

Allowing the use of OAuth Providers with duplicate basePath of token endpoint without scope parameter

We request further improvements to idea number APICONN-I-350 (https://ideas.ibm.com/ideas/APICONN-I-350).
Our problem is the same as with APICONN-I-350, but there was a condition where the scope was different even though the basic path
was the same at SBI, which had raised APICONN-I-350. For this reason, you made improvements to find out proper OAuth Provider by
adding scopes when making requests to token endpoints that have the same basic path.
However, RFC6749 does not state that scope parameter are mandatory when making requests to token endpoints. Nor are it also
defined as an Optional item.
Therefore, in the development manual for our fintech clients using our API platform, we did not state that scope parameter was required
when making requests to the token endpoint, and development was carried out accordingly.
In other words, scope parameter was not provided when making requests to the token endpoint.
As a result, when migrating from APIC V5 to APIC V10, there was a need to modify the application to provide scope parameter, and
additional costs were incurred.
The OAuth Provider for API Connect should comply with the RFC. This is because other companies also believe that API Connect
complies with the RFC and have development guidelines based on it.

Idea priority Low

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.