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 Delivered
Workspace WebSphere Liberty
Created by Guest
Created on May 9, 2018

Netcool Impact which uses WAS allows SSL communication even though the hostname is invalid in the Personal Certificate

Case number: TS000158115

Netcool Impact uses an embedded WAS

WAS start/stop SSL: WAS L3 answered that a new RFE is needed.

"This request is that the Netcool/Impact server startup, via WAS, must implement SSL hostname certificate verification
a. By default when the Impact Server/GUI processes are started there should be a hostname validation of the Personal Certificate.
b. Should there be an invalid certificate the Error message should be logged by default in the Impact logs without putting it in the “debug” mode.
c. A variable should be present within the WAS Liberty configuration if set to say eg: TRUE then it wouldn't start the Impact processes if the certificate hostname is invalid in the certificate , whereas if set to FALSE it will allow the Impact processes to still start .

As discussed in IBM-Citi call the reason we require a variable to control the starting/stopping of the Impact processes is because in a Production environment if an issue occurs we don't want the Impact processes to get affected .
Also as the Error messages shall be logged into the Impact logs we will be able to pick up the issue via monitoring

Idea priority High
RFE ID 119818
RFE Product WebSphere Application Server
  • Guest
    Oct 29, 2021

    It is possible to configure Liberty to do hostname verification as of This can be set on the ssl element by setting the verifyHostname attribute value to true.