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.
See this idea on ideas.ibm.com
Currently, when the z/OS Connect supplied authorization interceptor is enabled, we need to configure AdminGroup, OperationsGroup and InvokerGroup explicitly with RACF Group names which will then have respective permissions. The User IDs attaching to the respective RACF Groups, will get authorization to API services & requesters. But this brings considerable access management overhead. For eg: If a CICS screen invokes the API requester APIs, all User IDs accessing this CICS function needs to be added to the InvokerGroup to successfully invoke API requests (Especially when IdAssertion is enabled.)
So, we would like to have a feature that provides flexibility to configure access for “ALL” IDs, instead of specifying RACF Groups. This simplifies access management challenges, especially with InvokerGroup, when the invocation happens from trusted entities.
Example of desired configuration:
<zosconnect_apiRequesters location="path/to/apiRequesters" updateTrigger="disabled" pollingRate="60s" >
<apiRequester name=”sample” requireSecure="false" requireAuth="false" idAssertion="ASSERT_ONLY" invokerGroup=”ALLOW_ALL”> </apiRequester>
</zosconnect_apiRequesters
Idea priority | High |
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.
This requirement is addressed by z/OS Connect V3.0.55 / APAR PH436228:
https://www.ibm.com/support/pages/apar/PH43628
For further details, refer to the z/OS Connect(OpenAPI 3) Documentation:
https://www.ibm.com/docs/en/zos-connect/zos-connect/3.0
This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in future zOS Connect (OpenAPI 2) releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.