This is an IBM Automation portal for Integration 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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
As Pierce stated, in DataPower, PKIX validation can be performed with the root certificate in the Validation Credential (trust store) object. This means that if the certificate chain is leaf -> intermediate -> root (trusted CA), DataPower can still validate the client certificate even if the trust store contains only the root certificate. It's fine as long as the client presents the entire certificate chain, including the intermediate certificate(s), during the TLS handshake.
I am marking this as "Functionality already exists" based on the fact that DataPower has the ability to validate using the root certificate. This capability allows DataPower to successfully validate client certificates without requiring the intermediate certificate(s) to be stored in the trust store.
If you have a different requirement or use case that is not covered by this existing functionality, please provide more details and we can evaluate further.
Hi Thank for the comment.
For AWS end they will auto renew the intermediate and the base certificate without anyone knowing.
Therefore, without the correct base or intermeidate certificate, the PKIX mode will not work if it just root to root validation CA.
The PKIX mode just does what you are requesting. As long as the server is sending its intermediate CA certificates along with its leaf certificate, the Validation Credentials object just needs to contain the root CA.