This portal is to open public enhancement requests against IBM Z Software 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
This requirement is addressed by z/OS Connect Enterprise Edition V3.0.51 / APAR PH41351:
https://www.ibm.com/support/pages/apar/PH41351
For further details, refer to the Calling an API secured with OAuth 2.0 ”topic in the z/OS Connect EE V3.0 Documentation:https://www.ibm.com/docs/en/zosconnect/3.0?topic=options-calling-api-secured-oauth-20
We also have the requirement for different content types and credential locations. We tried sending the credentials as header, and a body with additional claims for realm & auth_method, but the body was not sent in the request. It also defaulted the Content_type to application/json, and we have a requirement for other content types, for example: application/x-www-form-urlencoded.
We utilize an in-house authorization server, which requires some custom claims be passed in. Examples of custom claims: “realm” and “auth_method”, so we have the need for a more generic approach.