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 Jun 8, 2020

RELATED IDEAS

support for 'scopes' as available in OAUTH2.0 standard

z/OS Connect Enterprise Edition currently supports OAUTH access_token to authenticate a requester, but it doesn't support 'scope' to authorise a request.
The https://tools.ietf.org/html/rfc6749#section-3.3 explains about scopes.
With help of 'scopes' it is possible have a central service (authorisation server) control access to all APIs across the total enterprise. Independent of where the API resides. The same principle will apply to z/OS exposed APIs as well to cloud-hosted APIs.
With help of 'scopes' z/OS Connect only needs to validate an access_token (authenticate) and check whether the right 'scopes' are attached (authorisation). Any client (client_id) must authenticate against the central authorisation-server at first and ask for an access_token associated with one or more scope(s) before it can initiate an API request to a z/OS Connect exposed API. The central authorisation-server will do the heavy lifting. z/OS Connect only needs to validate an incoming access_token and check whether it holds the right scope(s) required for the exposed API.
Per exposed API the required scope(s) could be different. Even per method (PUT, GET etc) used. The OAS3.0 specification provided per exposed API must be used to inform z/OS Connect of the correct security requirements per API and per method.

Idea priority High
  • Guest
    Reply
    |     Jul 20, 2020

    Whilst this requirement is valid, based on our current plans and priorities for IBM z/OS Connect Enterprise Edition, it is not likely that this could be implemented in the next 12 months. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

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.