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 Sep 28, 2018

Authentication and identity propagation for API Requesters

It's impossible to flow an identity end to end in the case of outbound, while for inbound it's smooth and allows to integrate heterogenous systems (Windows, Siebel, etc.) using standard modern protocols. All currently proposed authentication methods allow the user authentication only for separate steps during an outbound connection, but it does not allow to propagate user identity between steps. Another drawback is proposed user authentication methods, we have to supply full user credentials (user name/password), this makes the authentication for outbound practically useless in the real-world scenarios when we need to authentication the actual end user.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 22, 2021

    This requirement is addressed by z/OS Connect Enterprise Edition V3.0.43 / APAR PH34379:
    https://www.ibm.com/support/pages/apar/PH34379
    The z/OS Connect EE API requester is enhanced so you can generate a JWT, which contains the z/OS application asserted user ID as the "sub" (Subject) claim. For further details about this, refer to the “Calling an API secured with a locally generated JWT”topic in the z/OS Connect EE V3.0 Knowledge Centre
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/securing/requester_local_jwt.html

  • Guest
    Reply
    |
    Nov 26, 2018

    This is a major roadblock to deployment in our environments where we'd pass primarily batch id's.

0 MERGED

Support encoding/encryption of BAQPASSWORD for IMS & z/OS application outbound

Merged
In z/OS Connect EE API requester, if requireSecure="true" and requireAuth="true" and are not overridden, then the "users" need to authenticate. There are multiple authentication mechanisms that can be used, but the most common would probably be Ba...
almost 6 years ago in z/OS Connect 1 Delivered
0 MERGED

z/OS Connect EE: Allow to pass basic authentication credentials directly as parameters in request structure for API requester

Merged
For all API requester calls (outbound) we need to authenticate users using basic authentication (user + password) at the z/OS Connect level. Now, it's only possible using an user exist. This approach is complicated. We want to be able to pass cred...
over 6 years ago in z/OS Connect 1 Delivered
0 MERGED

Propagation USERID between ZCEE and API Provider

Merged
When i use API Requester, the USERID is not propagated. The future version will propagate the USERID between z/OS application and ZCEE but it lost after. My RFE concerns the part between the ZCEE and API Provider.
almost 5 years ago in z/OS Connect 2 Delivered
0 MERGED

zCEE – Allow basic authentication credentials to be passed in the request structure and not only the zosconnect_authData tag

Merged
When configuring basic authentication for z/OS Connect endpoints we only get the option to do this via the zosconnect_authData tag in the server configuration. This causes a couple of issues. - More endpoint definitions needed because we need the ...
over 4 years ago in z/OS Connect 1 Delivered