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 Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Dec 12, 2021

RELATED IDEAS

zCEE - mechanism to pass parameters to zosconnect_authToken

We are using the zCEE to retrieve a JSON Web Token (JWT) from a third-party authorization server and pass it on a request to an API endpoint, as described here:
https://www.ibm.com/docs/en/zosconnect/3.0?topic=jwt-calling-api-secured-third-party
In our environment, for each API we call, we need to pass a different pair of values, called ID and secret.
This means that for each such API we need to code these zCEE XML elements:
zosconnect_authToken

zosconnect_authorizationServer

zosconnect_authData
The content of the authToken and authorizationServer is the essentially the same for each API apart from the ID and secret stored in zosconnect_authData
zCEE should provide a simpler way that requires less XML to define the setup for each such API, ideally a way of setting the ID and secret for each API and passing that to a common zosconnect_authToken used by all such APIs

Idea priority Low
  • Guest
    Reply
    |     Mar 23, 2022

    This requirement has been evaluated. Looking at current plans, it is not likely that this would be implemented in future zOS Connect releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in twelve months time if you wish it to be considered then.

  • Guest
    Reply
    |     Jan 24, 2022

    We are using the approach described here, shown in example B

    https://www.ibm.com/docs/en/zosconnect/3.0?topic=reference-configuration-elements#config_elements__tokenRequest

    In addition to needing to send an ID and secret, we also need to be able to set a scope and ideally any other required variable in the request to the authorization server.

    We only need to send authentication credentials to the authorizationServer in the body of the request.

  • Guest
    Reply
    |     Dec 12, 2021

    Attachment (Description)

    2021 IBM Case E...
    2021 IBM Case Example zCEE Outbound API Client Secret V1.1.pptx
     2021 IBM Case Example zCEE Outbound API Client Secret V1.1.pptx
    Open full size
    2021 IBM Case Example zCEE Outbound API Client Secret V1.1.pptx

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.