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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Apr 1, 2021

RELATED IDEAS

Finer grain client request API Security

The feature request that we'd like IBM to explore is to provide the capability for zOS to be able use claims in an ADFS token to determine whether or not a given request should be given access to an API or Service. At the current moment, Liberty inspects the token and passes only partial information over to the zOS side ( audience information) but no claim (entitlement) for what action is allowable. The system in its current form only provides authentication and not authorization and relies on heavily customized changes on the backend which runs counter to the firm's forward stance on identity & access management. What we'd like is if liberty can pass on the token claims and then on the zOS side we can create interceptors to check for those claims to allow execution of that process.
At the moment, to have a token, is to have complete access, so preventing someone from having write access to an API based on what they requested in an entitlement system (claims that they own) is difficult as we can only check for openidConnectClient audience which is permissionless.

Idea priority High
  • Guest
    Reply
    |     Mar 23, 2022

    This requirement is addressed by z/OS Connect V3.0.55 / APAR PH43628: https://www.ibm.com/support/pages/apar/PH43628
    For further details refer to the “ Securing z/OS Connect resourses ”topic in the z/OS Connect OpenAPI 3 Documentation: https://www.ibm.com/docs/en/zosconn/zos-connect/3.0?topic=securing-zos-connect-resources

  • Guest
    Reply
    |     Aug 10, 2021

    Thank you for this RFE.

    Following assessment by our team we have identified a number of distinct requirements within this RFE:
    1) The ability to control authorisation at the API operation level
    2) The ability to pass JWT claims to the target z/OS subsystem
    3) The ability to base authorisation checks on claims within the JWT

    1 & 2 are part of our future plans
    3 we are investigating what would be possible.

    As such we have moved this RFE to Uncommitted Candidate state.

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.