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.20 / APAR PH09950:
http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI99563
Multiple group names can now be specified for the invoke, operations and reader authorization groups. This enhancement applies to both the global authorization attributes on the zosconnect_zosConnectManager element, as well as for specific authorization attributes on the zosconnect_zosConnectAPIs > zosConnectAPI, zosconnect_services > service, zosconnect_zosConnectService and zosconnect_apiRequesters > apiRequester elements. Multiple group names were already supported for the administration authorization groups.
For further details about configuring API authorisation, refer to the “API provider authorisation” topic in the z/OS Connect EE V3.0 Knowledge Center:
https://www.ibm.com/support/knowledgecenter/en/SS4SVW_3.0.0/securing/provider_authorization.html
Being able to use a RACF profile for authorization instead of naming RACF groups in server.xml would be even better as it would allow the security team to maintain authorization completely within RACF instead of needing to name groups in server.xml. Possible RACF classes for such a profile could include FACILITY or SERVAUTH.