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 Nov 29, 2019

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit ZCEE-I-245 Authentication and identity propagation for API Requesters.

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 same endpoint multiple times but with different credentials
- There is no good way to stop API requesters from using another endpoint with different credentials.
- Managing the credentials becomes a manual procedure. For SOAP requesters we have a program that automatically places user credentials in the header.
- No way to encrypt the server.xml and encrypting the password via SecurityUtility has some drawbacks.

Ideally we would like to be able to pass the zosconnect_authData credentials in the request structure of our CICS programs. Another solution would be integration with a user and password vault.

Idea priority High
  • Guest
    Reply
    |     Jan 2, 2020

    Currently with API Requester credentials can be passed from the mainframe application to the z/OS Connect EE server to retrieve an authentication token which is then used to authenticate with the remote API. We already have the ability to assert the identity and RFE 125402 is planned for a future release to use this identity as part of a token sent to the remote API. This offers a more secure process then sending passwords between systems and storing them internally and is our preferred method for identity propagation.

    As such we will be closing this RFE as a duplicate of RFE 125402
    http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=125402

    If you have any further requirements to those already stated in RFE 125402 please add them as a comment the RFE or open a new one to address any significantly different requirements.

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.