Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Planned for future release
Workspace PowerHA for AIX
Created by Guest
Created on Apr 8, 2020

PowerHA Gui remediation

we need support to remediate the following vulnerability report HA GUI clients

SSL Certificate with Wrong Hostname

RFE opened based on support recommendation , please see support update below

Unfortunately, the approach of generating new set of security files won't be an accurate solution as our existing security system is not designed to handle this approach. As per our existing design, GUI server generates a common SSL Certificate for all agent nodes and sends to all the agents while discovering cluster on GUI. So, all the agent nodes will always have a SSL certificate with server IP as Common Name(CN) instead of agent IP which Nessus tool will keep flagging in the scan.

We have tried our best to provide a re-mediation for this vulnerability but it looks like we would have to change the complete security design implementation that can only be done on a release boundary.

Idea priority Medium