This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
So it seems libvem passed the cafile parameter to openssl but the soam library doesn’t pass the cafile parameter to the openssl library.
Would you check?
This is currently a serious issue as the intermediate CA expires every 40 days, and it causes the client failed to connect.
In our aws cluster, the hosts’s certificate has intermediate CA and root CA, the root CA is the corporate CA and seldom change, but the intermediate CA may change. For now we put both intermediate CA and root CA in the CA file for the symphony client and it works fine. But lately the intermediate CA changed in the AWS hosts and cause break.
We found that we must put intermediate CA in the client side, even in the master host we already put both certificate and intermediate CA. Is there any configuration that we can put only root CA in the client, that the vemkd should send both certificate and the intermediate CA for the client to verify.
Do not place IBM confidential, company confidential, or personal information into any field.