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 Jan 13, 2022

Userid information should be displayed in ZCEE Early Failure 401 Authorization requests logged by Omegamon/JVM

The ability to monitor early authorization failures HTTP 401 is now available in z/OS Connect and Omegamon/JVM but the userid and mapped userid is not displayed for these failure requests.

The userids are retrieved by using getUserPrincipal() which for an early failure 401 failing request will always return null as the userid has not been assigned to the thread as it isn't yet authorized. However the userids information is available as they are produced in STDOUT messages so they should be passed to Omegamon/JVM as this is the main monitoring tool to aid quicker problem identification and automated alerting of these failures etc.

Idea priority High
  • Guest
    Reply
    |
    Jun 29, 2022

    Thank you for raising this request. It is now addressed by z/OS Connect Enterprise Edition V3.0.58:

    https://www.ibm.com/support/pages/apar/PH46461

    https://www.ibm.com/support/pages/apar/PH46512

  • Guest
    Reply
    |
    Apr 27, 2022

    This is a very high priority for us as well. We process 130 million z/os connect API's a day thru 6 servers. It is impossible to enable a trace to capture this VERY valuable diagnostic information.