This portal is to open public enhancement requests against IBM System Storage 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.
CSM never "breaks" the connection to a z host except on a restart of the server. So if you did not see the new cert active it is likely because that connection has already done the SSL validation and handshake. After you restart the CSM server or the connection is lost and automatically reconnects.....then you should hopefully see the new certificate in place. If not then please open a case.
Hope that answers the questions.
Adding a z/OS connection and adding the certificates have been split into two different methods. When adding a secure connection via REST you first need to call the POST /storagedevices/zoscert method passing in the cert file. When calling this, there is no reference to the host it will be connecting to. This file is added to the trust store on the server. Then you call the PUT /storagedevices/zoshost method passing in the connection info to the zOS host.
If adding more than one z/OS host connection, the process is the same. First call the POST /storagedevices/zoscert and then the PUT /storagedevices/zoshost. The new cert passesd in will be appended to the trust store.
When modifying zos certs simply call the POST /storagedevices/zoscert.
If this still does not meet your requirements please let us know what you would like to see to help with your needs.