Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Future consideration
Categories Usability
Created by Guest
Created on Jan 2, 2023

OpenIDConnect : Embedded browser based authentication for UI based Non-Web clients

Context: ELM 7.0.2 deployed with Jazz Authorization Server which is delegating Authentication to a another OIDC Provider (PingID)

The Liberty Application Password (app-pwd) concept introduced, in order to support OpenIDConnect for non-web client is not a feasible solution for our users of EWM Eclipse client. The limitation of the pre-requisite of generating an app-pwd by the user individually for each of the applications in a multi-context root environment (e.g. CCM1, CCM2, CCM3 etc.) is too cumbersome for a user using the rich-client (like EWM Eclipse). If this user has Projects spread across in different context roots, she needs to switch the app-pwd in order to connect to the corresponding application. This is unacceptable in terms of usability. For such non-web clients, an embedded browser based solution will be way more user-friendly (similar features already present in Rhapsody - GC picker or in DOORS Classic). Without the embedded browser based authentication of UI based Non-Web clients, we will not be able to rollout to our users.

Note: The app-pwd feature usage for command-line clients (like ETM Adapters) however, is acceptable as this is mostly used for headless execution

Idea priority High
Needed By Month
  • Guest
    Reply
    |
    Jan 6, 2023
    Thank you for submitting this RFE for browser-based authentication in non-web clients. We've been considering this within our products and are making this RFE an uncommitted candidate for a potential future release.