Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

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.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Workspace Spectrum LSF
Created by Guest
Created on Sep 20, 2022

Create a User Interace and Process flow for API Key Generation, Approval, Use, and Revocation

We presently are evaluating Application Center's Web Services for job submission and control. However, many of our submission users are robots where the password is not known to user, but rather the users have sudo authority to submit jobs from specifically designated hosts. We would prefer to have the ability for a user to either request a long lived API key/Session key from the Application Center GUI for themselves, or the ability to request one for a service account. If for a service account, Application Center would forward an approval request to an administrator for approval, or if the API key request was made by the Application Center administrator, be approved and generated automatically. Once those API keys are generated, the Application Center Administrator should be able to: 1) See the list of keys, 2) When the key was last used 3) When it is due to expire 4) Request user and the execution user Then, they should be able to revoke one or more API keys via that interface at any time, and also be able to copy the actual API key to their clipboard without viewing the actual key for sharing with the request user.
Needed By Yesterday (Let's go already!)
  • Guest
    Sep 20, 2022

    currently PAC has internal API-Key concept-- generated when use logon. the u/p and key operation functions are done by 2 built-in libraries.

    the default expiration date for the key is 8 hours. the key is generated and saved in $HOME/.pacpass if user logon with u/p from pacclient (download from: . user could copy the key to any where and use it in Restful API. but we do not have consistence way/UI to manage the PAC API-KEY.

    discussed with user, if it is urgent, user could build the API-key management system by calling the PAC built-in libs from java. have sent the instruction to user about how to manage PAC Restful API-key using the libraries.