IBM Z Software
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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Whilst this requirement is valid, based on our current plans and priorities for IBM z/OS Connect Enterprise Edition, it is not likely that this could be implemented in the next 12 months. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.
Thank you for the clarification, and additional information. It will provide useful input as we look at the broader challenge of multi team environments.
creating yet more servers isn't the answer, we'd still have to secure every API and then have all the additional overhead of managing and maintaining yet more server instances. (and license them all).
The concept of groups would work, so connecting an API to an API group and then securing the group. That would also translate well when this all moves out of the server config into RACF which will hopefully happen down the line.
regards
Steve
Thank you for this requirement.
Firstly, I would like to know the reason why you could not just use different z/OS Connect EE servers to separate team access? This is a common pattern in development and test that many of our customers use to solve this problem.
If there are are infrastructural reasons why the same server must be shared between teams, would having the concept of an "API Group" enable you to solve this problem?
eg each API could be assigned to a group and then security and interceptor configuration could be applied to a group as a whole.
So rather than a wild card lookup with some naming convention you would simply assign APIs to group A or B for "Team A" or "Team B".