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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories Communications Server
Created by Guest
Created on Jul 11, 2025

RELATED IDEAS

Client Certificate validation on AT-TLS Server with client authentication

In AT-TLS, when the HandshakeRole parameter is set to ServerWithClientAuth, a certificate request is sent to the client during the handshake. The client can send its certificate to the server, which can then validate the certificate.

The level of validation done by the server is controlled with the ClientAuthType parameter on the TTLSEnvironmentAdvancedParms statement.

Considering this implementation, when validating the client Certificate on AT-TLS policies on Server side, would it be possible to require stronger authentication mechanisms like the ones below ?

In mutual TLS (mTLS) client authentication, the Common Name (CN) field in a client certificate is used to verify the client's identity because typically contains the individual's name, or a unique identifier for the client.  

Other attributes such as Subject Distinguished name (DN) or Subject Alternative Name (SAN) could be used with some of these fields as long as a desired value can be included:

   Subject Alternative Name DNS
   Subject Alternative Name IP Address
   Subject Alternative Name URI
   Subject Alternative Name Email
   Self Signed Certificate Key ID

 

 

Idea priority Medium
  • Guest
    Sep 25, 2025
    The best way to address this would be to make MQ an "AT-TLS aware" application (which can be done using existing Communication Server APIs). This idea will be declined.

    Please open an idea against MQ for making their application AT-TLS aware.
    Reply
3 MERGED

AT-TLS Check Client DNS in Certificate CN/SAN

Merged
Currently it is possible to define connection as requiring ServerWithClientAuth. This causes the TLS handshake to check that the client certificate is signed by a known CA. Can the configuration options for this check be extended to check that the...
6 months ago in z/OS / Communications Server 1 Not under consideration

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.