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

RSEAPI - Force session usage

Hello, 
APIs can be used either with basic auth or by opening a session using a token.

Some APIs, such as those that return session information, can only be called with a token.

The setting to limit usage, `POST /api/v1/admin/settings`, only applies to sessions and does not restrict calls via basic auth. Since auditing, `GET /api/v1/admin/session`, also only works with sessions, I consider the use of basic auth problematic from a security standpoint.

Is it possible to limit the use of basic auth?

To achieve this, I see two possibilities:

  • Allow basic auth only for obtaining a token, POST /api/v1/session, but this would force this choice on everyone...
  • Add a setting in the settings, POST /api/v1/admin/settings, "onlyToken", value true/false: 
    • true: only obtaining a token is possible with basic auth. All other authentication methods require a token.
    • false: the current behavior remains unchanged.
Idea priority Medium