Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Future consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Dec 15, 2023

Requirement to support HTTP header-based authentication with Z/OSMF

We are trying to access z/OSMF over an Apache HTTPD proxy, unfortunately the proxy does not allow us to forward the client authentication certificate. The authentication is done on the proxy and then the proxy forwards the HTTP header-based authentication ( UID/PW ) to z/OSMF but this does not allow a direct login to z/OSMF. Hence, the user still has to enter Userid/Password on the LOGON Panel of z/OSMF. 
This requirement is for z/OSMF to support HTTP header-based authentication with Z/OSMF. 

Background is that for some use cases we want to provide access to Z/OSMF through an Apache HTTPD proxy. For this scenario the use of certificate-based authentication does not work. 

The alternative is to use HTTP header-based authentication with a trusted proxy server. The user will be authenticated by our Single Signon solution (CA SiteMinder) on the proxy. Single Signon will add the user information into the HTTP header from where it should be read by Z/OSMF. Apart from specifying the headers to read, it should also be possible to restrict the IP/Hostnames to which Z/OSMF should trust.

Idea priority Urgent