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
z/OS Connect EE's authorization interceptor process internally requires all RACF GROUPs associated with the RACF ID that may belong to either Global Reader Group, Invoke Group, Operator Group, Reader Group to carry unique USS GID for successful validation.
A RACF may get associated with any number of RACF GROUPS (now or in future) and there is a potential those RACF GROUPS may have duplicate USS GID.
This request is to see, what is causing z/OS Connect EE to mandate UNIQUE GID for all RACF GROUPs and eliminate this. As required RACF GROUPs used part of Global Reader/Invoke/Operator/Reader are always specified part of server.xml entries, Why can't a RACF be validated just against those group names irrespective of whether they have UNIQUE or DUPLICATE USS GID..
Idea priority | Medium |
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 has been evaluated. This enhancement would encourage a behaviour that is not recommended:
"Although the same GID can be assigned to multiple RACF groups, it is not recommended. If you assign the same GID to multiple groups, control at an individual group level is lost because the GID is used in z/OS UNIX security checks. RACF groups that have the same GID assignment are treated as a single group during z/OS UNIX security checks.
You can enforce identity uniqueness when assigning UNIX identifiers. For more on controlling GID uniqueness, refer to Controlling the use of shared UNIX identities. A unique GID can be defined automatically using the AUTOGID operand, as described in Enabling automatic assignment of unique UNIX identities."
From: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.icha700/ussgid.htm
As such it is not likely that this would be implemented in future zOS Connect EE 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.