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 Delivered
Workspace z/OS Connect
Created by Guest
Created on May 25, 2020

z/OS Connect EE - Enable ID Assertion at individual API requester level

ID Assertion capability (to propagate security credentials from z/OS Applications onto z/OS Connect EE) got introduced with 3.0.24. It is a valuable one. But it can be configured ONLY at Global level (zosconnect_apiRequesters) within a runtime. That is, Once it is enabled, it will be applicable across all API requesters'. As API Requesters' of distinct nature to be created and security need for them as well be different, We strongly recommend to allow ID ASSERTION to be enabled/disabled at individual API Requester level (i.e., at apiRequester level).

Idea priority High
  • Guest
    Reply
    |
    Jun 10, 2021

    This requirement is addressed by z/OS Connect Enterprise Edition V3.0.45 / APAR PH36068:
    https://www.ibm.com/support/pages/apar/PH36068
    The z/OS Connect EE API requester is enhanced to allow you to specify the idAssertion attribute on the
    zosconnect_apiRequesters > apiRequester subelement for individual API requesters.
    For further details refer to the “additional configuration for the API requester archive” topic in the z/OS Connect EE V3.0 Documentation:
    https://www.ibm.com/docs/en/zosconnect/3.0?topic=reference-configuration-elements#config_elements__apiRequester

  • Guest
    Reply
    |
    May 26, 2020

    Strikes me that in an Operational Envt its vital that any setting for ID Assertion is consistent across all requestors (and in effect active). So on that basis I'm not supportive of this RFE.