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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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 Web Serving
Created by Guest
Created on Jun 12, 2024

Add user registry and TAI to RSE APIs


Concerning the use of Remote System Explorer APIs (RSE API), we currently use basic authentication + a session.

This opens up many possibilities (IFS access, SQL queries, CL command calls, etc.) to all users (within the limits of their rights, which are often too high).

We would like the same authentication system as with IWS: user registry (user, group, role) and Trust Association Interface (TAI).

A configuration file or GUI should be added to indicate for each service/route which roles are authorized.

Pre-established scopes could be defined for the services: ifs, sql, etc. and session creation could be limited to one or more scopes (information to be added to the call of the authentication service POST /api/v1/session).

All this would allow better control of the rights on these APIs

Idea priority High