Skip to Main Content
IBM System Storage Ideas Portal


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).


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 (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.

Status Under review
Created by Guest
Created on Apr 3, 2024

cert_distribute.sh script should allow customers to input a list of client nodes

In the current implementations, the cert_distribute.sh shell script at levels 8.1.21 and 8.1.22 queries the Storage Protect server for all its Storage Protect client nodes, does some filtering to select only supported platforms, and then will associate the queried nodes to the cert_renew_* schedules defined by cert_distribute.sh.
Using this implementation/ design, the cert_distribute.sh script is unable to detect that multiple Storage Protect client node names belong to the same hosts, maybe running multiple Storage Protect client schedulers, connecting to the same Storage Protect server.
As a result, multiple Storage Protect client schedulers will be associated to the same set of cert_renew_* schedules. Because of this, multiple client schedulers will execute the same scheduled command, trying to create and write into the same new client crt file in parallel. This will result into a corrupted new client crt file and invalidates the overall process of distributing the new SSL certificate to the Storage Protect clients.
An easy solution to this would be to allow customer to create a file containing a list of all Storage Protect client nodes which should receive the new SSL certificate. 
The cert_distribute.sh script should use the list of Storage Protect client node names out of the customized input file instead of querying all Storage Protect client nodes from the Storage Protect server itself. To ensure the customer only specified valid/ support Storage Protect client nodes the cert_distribute.sh script may validate the customized list against the Storage Protect server.

Idea priority High