Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Dec 5, 2022

DynamicInbound Endpoint SSL Config

Similar to the 'dynamic outbound endpoint SSL configurations' feature, it would be helpful to specify the SSL config and certificate used when WAS receives an inbound connection. As an L2 Support employee, I have worked cases where clients requested this feature.

Here's a certificate chain example scenario:

The loacalhost for WAS has two hostnames: and Both hostnames resolve to the same IP address. However, is a SAN name in the cert and vice-versa. They still want to make sure only the specific cert chain (depending on the client endpoint) is used for each SSL connection. This avoids adding two different signer certs in both the client's trust stores.

Here's a protocol scenario:

A client supports TLSv1.3 and TLSv1.2. WAS is also configured to support TLSv1.3 and TLSv1.2. It is possible that a customer would want their client app to only support TLSv1.2 with WAS (when WAS receives an inbound connection) and support multiple protocols with other endpoints. This feature would be an easy way for the customer to set that up.

The same applies to specifying an SSL config for specific ciphers when WAS receives an inbound connection.

Idea priority Low
  • Admin
    Graham Charters
    Dec 16, 2022

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. We believe a possible workaround is to use IHS in front of WAS - see Given this workaround and the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters <>.