Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Workspace z/OS
Categories RACF
Created by Guest
Created on May 12, 2025

Connect command shouldn't have a default owner

Problem

When you do connects in RACF and don't specify an owner it will default to the user id of whoever executed the command, this should be changed as it is not secure and can negatively affect uptime. This becomes an issue if a security administrator forgets to add an owner or doesn't know what they're doing, because then when the administrator leaves the company and their user gets deleted all of their connects will become orphaned, it can also be an issue if the administrator changes job withing the company and now suddenly owns connects they shouldn't be allowed to own anymore.

Proposed solution

Have connects without an explicit owner fail

This should fail:

connect cooluser group(BADDIES)

Above command should result in a message like "[insert weird RACF error code] connect failed, no owner was specified"

This should go through:

connect cooluser group(BADDIES) owner(SECADM)

 

I think this should just always be the behavior of RACF and not just an extra setting that can be turned on, it's too dangerous the current way it functions.

Idea priority Medium
  • Guest
    Jun 3, 2025
    The owner specified on the CONNECT command does not factor into authorization decisions. However, we do feel the documentation could be updated to clarify this.
  • Guest
    May 20, 2025
    Thank you for submitting this Idea. Can you provide more details on the perceived security risk?