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
Created by Guest
Created on Oct 20, 2019

Cert expiry on 119-12

Currently the zERT summary SMF record (type 119 subtype 12) lacks some of the certificate details that are present in the detail record (type 119 subtype 11). I propose that all details collected by the detail record be propagated into the summary record - particularly the certificate serial number and expiry (or "not after") date. I concede that within a "session interval", more than one client or server certificate might be detected, so I'm happy if the details reported pertain to the first connection or the most recent connection seen (i.e. the captured data is overwritten by each new connection). I don't think much value is derived from trying to detect the certificate with the earliest "not after" date, for those (rare) circumstances where multiple certificates are detected in a single session interval.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 30, 2020

    This item is not in our plans but is being kept in our backlog.

2 MERGED

More info about certificates and keyrings in connection analysis in zERT.

Merged
It would be very useful for a z/OS security group to identify quickly what certificate and keyring is being used in a connection. We know that currently we have the DN that uniquely identifies the certificate but it would be easier and faster if w...
4 months ago in z/OS / Communications Server 1 Future consideration