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 Not under consideration
Workspace z/OS
Created by Guest
Created on Apr 19, 2024

Add Certificate Information to TLS command

When updating our certificates in our environment we would use a packet trace to confirm that our certificate updates occurred. This method worked since in TLS 1.2 and earlier the Server Hello would have the certificate in visible in the flow.

However, with the TLS 1.3 this is no longer possible as the TLS handshake encrypts all certificates that are being sent. At this point we can no longer use the technique that we used before to verify proper certificate updates. Note that we can not use the SMF type 119 sub 11 records as we do not have that on due to the volume issues it would cause. The sub 12 records do not have the Certificate date information.

Idea priority High
  • Guest
    Reply
    |
    Oct 9, 2024

    This is still going to be an issue as due to our volume we can capture type 12 records.  We are now starting to move aggressively to TLS 1.3 .  There is no reason that a control block could not include the certificate information and displayed as part of a dynamic command.   

     

    1 reply
  • Guest
    Reply
    |
    Apr 26, 2024
    One workaround would be to use zERT enforcement to cut a zERT detail record for connections of interest. Also, the following requirement might also be helpful if implemented, so consider voting for it:
    Idea ZOS-I-339 "Cert expiry on 119-12" https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-339