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 Jun 18, 2014

AT-TLS support for limiting which client certificates that are allowed to use an specific IP port

We need to be able to use AT-TLS with client and server verification of certificates.
We need to be able to limit which client certificates we allow to connect and use this IP port so that not all certificates from a CA in our truststore (keyring) is allowed.
We plan to use this feature in conjunction with IMS Connect, the purpose is to be in control and know exactly which application (on certificate base) we trust to connect to IMS Connect on this specific IP port.

Idea priority High
  • Guest
    Reply
    |
    Apr 19, 2024
    This item is unlikely to be given high enough priority to be placed into product plan.
  • Guest
    Reply
    |
    Dec 7, 2015

    I support this request. We have an similar scenario with a remote client promoting at application level pre-authenticated user information without full credentials to a z/OS task over an AT-TLS connection, and therefore requiring this client to be trusted by z/OS. We need the RACF user id derived from the client's certificate to be checked whether it is allowed for the connection. Since we have a requirement to use AT-TLS for TLS support wherever possible (central management, up-to-dateness), we need to make AT-TLS check this. I suggest to extend the SAFCheck option of ClientAuthType by a new parameter safname. AT-TLS might then check SAF profile, e. g. EZB.ATTLS.sysname.tcpname.safname of class SERVAUTH, for READ access with the user id derived by SAFCheck from the certificate and then allow or close the connection with regard to the RACF return code.

  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server