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 Under review
Workspace IBM i
Categories Security
Created by Guest
Created on Feb 25, 2026

Develop a way to signon via QSECOFR account with a password less solution for ACS, Console and web-based applications.

This is To Comply with Audit requirement to enforce all Privilege Access accounts to move away from visible Passwords .

Idea priority High
  • Guest
    Aug 19, 2026

    Thank you for taking the time to submit this IBM Idea and share your feedback with IBM and the broader IBM i community.

    The CAAC has reviewed this Idea and, after careful consideration, does not recommend that IBM move forward with the request in its current form at this time.

    Reason: The CAAC recognizes the importance of reducing password exposure and meeting audit requirements for privileged access. However, the council does not recommend enabling passwordless direct sign-on with QSECOFR, given the profile’s extensive system authority and the need to maintain strong individual accountability for privileged activity. The preferred approach is for administrators to use individually assigned profiles with the appropriate authorities and supported enterprise authentication mechanisms, rather than signing on directly with the shared QSECOFR profile. The CAAC believes the underlying requirement may be better addressed through secure, auditable passwordless authentication for named privileged users.

    Although the CAAC is not recommending implementation of this request, Ideas such as this help IBM and the CAAC better understand the needs and priorities of the IBM i community. We appreciate your contribution and encourage you to continue submitting IBM Ideas and sharing your feedback.

    Background: The COMMON Americas Advisory Council (CAAC) includes members with a broad range of experience working with small and medium-sized IBM i clients. The CAAC works with IBM i development to help assess the potential value and impact of individual IBM Ideas on the broader IBM i community.

    For more information on the CAAC, visit: https://www.common.org/common-americas-advisory-council/

    Brandon Pederson - CAAC Program Manager

  • Guest
    Mar 17, 2026
    IBM has received your Idea and is evaluating allowing QSECOFR password to be set to *NONE. IBM will provide a response after evaluation is complete.

    IBM Power Systems Development
  • Guest
    Mar 5, 2026

    Could you use IBM i EIM / SSO to achieve this?

    https://www.ibm.com/docs/en/i/7.6.0?topic=s-scenario-enabling-single-sign-i
    PS Hopefully you would not do it with QSECOFR, as best practice is to have this user disabled but we certainly do this for our *SECOFR SysAdmin users.


    Best wishes,
    Steve Bradshaw
    The Friendly Techie at RowtonIT.com
    IBM Champion, Member of CEAC, TD of i-UG.co.uk