Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Feb 5, 2024

z/OSMF workflow engine to provide access to zOSMF JWT/LTPA token

When creating a zOSMF workflow step that invokes an External RESTapi, it would be useful to have access to the current z/OSMF user's JWT token in order to use the bearer token in an API call for other z/OS services.  APIs that go through Zowe's API/ML can configure zOSMF as the security provider to validate the JWT token.  If the JWT token is enabled via a secured cookie, the token can then be leveraged in a subsequent API call.  Similar support is available when creating a zOSMF plugin, it's just not available using the workflow engine.  Currently, the only available means for REST calls from the Workflow engine is to use basic auth credentials or a client certificate.  Using Client certificates would be next to impossible for users to manage for all zOSMF users.  Basic auth credentials would mean that the user had to be prompted for each invocation of a REST API call from the workflow engine.  Saving the credentials in a workflow variable wouldn't be a good choice either as the credentials may contain one-time use passwords authenticated through MFA.  

Idea priority High