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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
I am writing this comment on behalf of a customer. In many companies, in order to comply with the security rules a TLS certificate needs to be signed by an internal intermediate CA. This internal intermediate CA and the internal root CA are then added to the truststore. The issue with this approach is that there may be a lot of TLS certificates signed by the same internal intermediate CA, and they may be used by client applications that must not have access to the CTG server.
It is not possible to only add the authorized client certificates to the truststore, as during the TLS handshake the authorized signer are provided, and since the client certificates are not self-signed (in this usecase) the client application may choose to comply with eligible signers and not send its client certificate.
A possible workaround is to create a dedicated internal intermediate CA for the CTG server, but this implies creating an exception or making a special case for the CTG users.
It would be really helpful if there is a way to filter out authorized clients from unauthorized clients, through CTG configurations.