IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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 https://www.entrust.com/resources/certificate-solutions/tools/root-certificate-downloads
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
Do not place IBM confidential, company confidential, or personal information into any field.