Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 IBM i
Categories Db2 for i
Created by Guest
Created on Dec 8, 2022

Require QIBM_DB_SECADM or similar to perform set session authorization

Today any user with *ALLOBJ is able to do the equivalent to sudo in Linux without the need of any password to become another user using set session authorization via SQL. Any user with *ALLOBJ can become Qsecofr by open strsql and run: “Set session authorization Qsecofr”. I propose that only users with special authorization QIBM_DB_SECADM or similar would be able to do this, at least for elevated users.

Idea priority Urgent
  • Guest
    Reply
    |
    Mar 24, 2023
    IBM does not intend to provide a solution to this Idea at this time, so it is being closed.

    SET SESSION AUTHORIZATION is an SQL statement that swaps the effective user of the current thread to be running as a different user.
    Documentation: https://www.ibm.com/docs/en/i/7.5?topic=statements-set-session-authorization
    The SET SESSION AUTHORIZATION requires *ALLOBJ special authority, and an AF-K audit journal entry is generated if a user without *ALLOBJ attempts to use it.
    The SQL statement is implemented via calls to QSYGETPH (using Password_NOPWDCHK) and QWTSETP.

    ? Get Profile Handle (QSYGETPH) validates a user ID and password, and creates an encrypted abbreviation called a profile handle for that user profile.
    ? Set Profile Handle (QWTSETP, QsySetToProfileHandle) switches the job to run under a new profile.
    *NOPWDCHK:
    - The user requesting the profile handle must have *USE authority to the user profile.
    - If the profile is disabled, the user requesting the profile handle must have *ALLOBJ and *SECADM special authorities to get a handle.
    - If the password is expired, the user requesting the profile handle must have *ALLOBJ and *SECADM special authorities to get a handle.

    SET SESSION AUTHORIZATION and Set Profile Handle have a common security authorization requirement, which always includes *ALLOBJ, and sometimes includes *SECADM.
    To add an additional function usage authorization requirement to one of the interfaces would create a chasm in security implementation.
    Such an additional requirement to security would also likely break many existing software vendor products and customer solutions.
    It is for these reasons that the IBM i security team and Db2 for i team are rejecting this idea.
  • Admin
    Nancy Uthke-Schmucki
    Reply
    |
    Jan 31, 2023

    The CAAC has reviewed this IBM Idea and recommends that IBM view this as a high priority Idea that is important to be addressed. From a security perspective, this is a valid request.


    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual IBM Ideas on the broader IBM i community, and has therefore reviewed your Idea.


    For more information about CAAC, see www.common.org/caac


    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Jan 5, 2023
    IBM has received your Idea and is evaluating it. IBM will provide a response after evaluation is complete.
  • Admin
    Sabine Jordan
    Reply
    |
    Dec 8, 2022

    The CEAC agrees with the sentiment of this idea but would suggest that any user with this concern looks to remove all unnecessary users with *ALLOBJ authority. IBM added Authority Collection Services in IBM i 7.3 to assist with this process.a

    Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Sabine Jordan + Sara Anrdres – CEAC Program Manager, IBM



  • Guest
    Reply
    |
    Dec 8, 2022

    inadmisible