Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Future consideration
Categories Security
Created by Guest
Created on Dec 18, 2025

specifying also issuing CA name of client authentication certificates in remote nodes

when I define a certificate common name for client authentication in a Remote Node, there's no possibility to add the name of issuing certificate authority.

this means that authentication will be successful for 2 or more different certificates with identical common name (e.g. CERT1) as long as for all these certificates their root/issuing certificates are stored as trusted certificates in the keystore.

this imposes a possible security risk.

What is your industry? Banking
How will this idea be used?

to enhance security by ensuring that the certificate common name belongs to a specific issuing CA and cannot be mixed up with other identically named certificates.

  • Admin
    James Joseph
    Dec 18, 2025

    We are accepting the idea and considering it future releases. we can revisit this once we see the traction from other customers and partners (via Voting or Comments). Thank you for your patience and co-operation.

    Thanks,

    James

  • Admin
    James Joseph
    Dec 18, 2025

    Thank you for taking the time to share your ideas to IBM. We truly value our relationship with you and appreciate your efforts and willingness to share details about your experience, your recommendations, and ideas. We will soon review the same in the coming weeks and shall get back with a response.


    Thanks,

    James