Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Under review
Workspace z/OS Connect
Created by Guest
Created on Apr 23, 2024

Add bootstrap loading of JWTs in cache and also enable pro-active refresh of bootstrapped JWTs

To decrease latency while procuring JWT tokens when a API request is made to z/OS Connect, its better to implement below logic & provide it as a configurable choice:
* Create a list of OAUTH claim requests in a file that will be read by z/OS Connect on boot
* Then, z/OS Connect connects to JWT issuer endpoint to procure the JWT tokens and populates cache
* When COBOL/mainframe application makes an API request call to z/OS Connect with one of OAUTH claim, z/OS connect since it pre-cached the JWT, it reuses the existing JWT from cache and forwards the call to the API provider endpoint without much added latency
* z/OS Connect also pro-actively refreshes the JWT before its expiry by procuring the JWT using the same list used during the bootstrap process.  

Idea priority High