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.

Add a new idea Subscribe
Status Future consideration
Workspace z/OS Connect
Created by Guest
Created on Oct 26, 2022

RELATED IDEAS

API Requester Security flow jwt-bearer

With the two OAuth flows supported today by z/OS Connect:

  • Client credentials (client_id + client_secret)

  • Resource owner password credentials (client_id + client_secret + username + password)

If we want to call a remote API from a mainframe application with an end user identity, that application needs to know the end user password to use the Resource owner password credentials flow.


The “jwt-bearer” flow would allow to get a token from the authorization server which represents the end user without the need for that application to know the end user password because only the end user ID is sent to the authorization server in a JWT format.

  • Information sent to the authorization server are:

    • Client ID

    • Client password

    • JWT with sub claim equals to the end user ID known by the application

The request to the authorization server would look like this:

grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&

client_secret=<secret>&

client_id=<clientId>&

scope=openid&

assertion=eyJhbGciOiJFUzI1NiIsImtpZCI6IjE2In0.eyJpc3Mi...

And client_id:client_secret could also be in the HTTP authorization header in a basic authorization format.


In response to the authorization server, z/OS Connect will receive an access_token which represents the end user identity.

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.