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

z/OS Connect

Showing 243

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 th...
over 1 year ago in z/OS Connect 0 Future consideration

Make it possible to send an empty body with other http response code then 204 (no content)

Seems that when you use http response code other than 204 and you remove the body in your mapping that there is always a body of the tags above.It should be possible to define whether you want a body or not. For example: we want to use 202 without...
6 months ago in z/OS Connect 1 Functionality already exists

Remove parent tags from input and output bodies

When you make a API with an input body (JSON), you always have to give the parent tags of the service instead to those that really are related to the content of what you want.Same for the output body (JSON), where those parent tags are always show...
6 months ago in z/OS Connect 1 Functionality already exists

Support for IMS transaction name length required

Our site uses variable length IMS transaction names.The current implementation of the API Toolkit with fix PH09920 allows to specify a transaction name that will either be padded with spaces for a maximum length of 8 characters or if the Space Del...
almost 3 years ago in z/OS Connect 3 Not under consideration

Health checker for z/OS Connect Endpoints

Health checker for z/OS Connect Endpoints.
almost 5 years ago in z/OS Connect 2 Not under consideration

Provide meaningful error messages for z/OS Connect and API toolkit problems

Currently z/OS Connect provides for a lot of configuration errors, RACF and Unix System Services problems neither an error message in the JES Job Log nor an error message in the messages.log. Often the only way to get an impression of what may be ...
almost 7 years ago in z/OS Connect 4 Not under consideration

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 applica...
about 2 years ago in z/OS Connect 0 Future consideration

zOS Connect enable generics in zosConnectAPI name construct

in order to secure API using the authorizationInterceptor for access by different teams we currently have to specify every API and define the relevant access. With naming standards we can group these much more efficiently using generics for exampl...
over 5 years ago in z/OS Connect 4 Not under consideration

z/OS Connect Field/Header Validation

Provide basic validation for input API fields.
about 3 years ago in z/OS Connect 2 Not under consideration

Add the support of required field in APIS Body

We need to force APIs consummer to provide mandatory fields in the JSON body of an APIS.This is really important for APIS that use a MQ service because in this case we have no way to check fields before the message is PUT in the queue by the servi...
almost 3 years ago in z/OS Connect 2 Future consideration

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.