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 Future consideration
Workspace z/OS Connect
Created by Guest
Created on Jul 18, 2023

z/OS Connect to support the token being returned from the authorization server in a custom field in an OAuth 2.0 flow

We are using the z/OS Connect OAuth 2.0 support to obtain an access token from our EUA Authorization server. This retrieves the access token from the “access_token” field of the JSON response, as per the OAuth 2.0 specification. In the response there is also an ID token in an “id_token” field, and our specific requirement is to retrieve this ID token (a JWT) and transmit it to the API endpoint instead of the access token. The ID token is the primary extension that OpenID Connect makes to OAuth 2.0. The “id_token” response is defined in “OAuth 2.0 Multiple Response Type Encoding Practices”: https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html.

This enhancement is useful as it allows for an increased flexibility and customization for organizations who require the ability to retrieve an identity token rather than an access token from OAuth 2.0 authorization servers allowing for seamless integration and accommodating diverse authentication needs. 

 

Response from EUA to Client:

    HTTP/1.1 200 OK
   Content-Type: application/json
   
   {
       "access_token": {access-token},
       "token_type": "Bearer",
       "expires_in": 3600,
       "id_token": {identity-token}
   }

Idea priority Medium