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
Created by Guest
Created on Sep 16, 2025

Azure: Add OAuth Bearer Token Support

Currently, the CDA product supports several authentication methods, but it does not support OAuth. In order to support the existing authentication methods, like "SharedKey", Azure admins would have to enable settings that they otherwise might have disabled due to corporate policies. OAuth is an industry standard authentication method. In order to do this, the CDA product would need to make a REST API call to retrieve a token and then make a subsequent API call with that token in the authentication bearer header of the call.

An example REST API request for an OAuth Bearer token:

POST https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token

Request Body (x-www-form-urlencoded):
"client_id": "<client_id>"
"client_secret": "<client_secret>"
"grant_type": "client_credentials"
"resource_id": "https://storage.azure.com/"
"scope": "https://graph.microsoft.com/.default"

 

Users would be asked for the values to the various keypairs above OR they would simply need to update the provider file with any necessary keypairs above to be used in the token request. The latter would mean that token requests can be designed by users, rather than forced to conform to something within code.

Sample Response:

{
   "token_type": "Bearer",
   "expires_in": 3599,
   "ext_expires_in": 3599,
   "access_token": "<bearer token>"
}

 

The CDA product would take the <bearer token> from the "access_token" key above and use it in the authentication header.

Idea priority Medium