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 (

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
Created by Guest
Created on Feb 4, 2021

Require MEIG to perform certificate matching on unique values

In a scenario where multiple CA certificates having the same value for the DN Subject parameter exist in the database, MEIG can retrieve the wrong CA certificate and cause a valid Trading Partner certificate to incorrectly be interpreted as invalid due to errors relating to an empty trustAnchors parameter.

There are 2 scenarios where this issue might be encountered:

1) The one we observed where Entrust are using 2 different root CAs with same DN to issue EV vs non-EV certs.

Refer to

2) During CA renewal - the CA might reissue their new CA cert with same DN in say June - you might have one trading partner with a cert from May, one from July, and it won't work

It appears to be a design flaw in MEIG's certificate matching logic to rely solely on DN which may not be unique, and also not iterate through all available matching DN's. A more reliable design would be to match against authority key identifier and subject key identifier,

and/or iterate through all DNs that match.

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

As a vendor with a certificate that has a DN Subject matching another vendor's certificate DN Subject, I need my certificate to be recognised and allow me to transact with this government agency

  • Guest
    May 27, 2021

    This issue has also been encountered during a certificate change in our ebMS/AS4 gateway and necessitated a creative approach and significant on call support effort and cost to investigate, understand and fix resultant messaging issues caused by the current certificate management implementation