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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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 Sep 30, 2022

Password and Certificate expiration warning

Providing a warning starting at 30 days out and decrementing by week until the last week, then daily, would alert Users in advance of expiration.

Idea priority Medium
  • Guest
    Jul 11, 2024
    Will reconsider this request
  • Guest
    Oct 3, 2022
    While I understand the reasoning behind this request, I unfortunately do not think it's feasible across all CSM environments. CSM does not "manage" certificates. Certificates can be updated on the server or HMC that csm is running on, however these are stored in a keystore and used by the underlying Java/WAS architecture when creating a secure connection. I do not think CSM should be accessing this keystore regularly and as it's possible to have multiple certs, this could result in false positives leading to bigger problems. On HMC installs, CSM doesn't control the keystore either, as CSM communication is controlled through a proxy on the HMC so that all communication can use the same keystore.

    CSM's default cert was previously created with an expiration "years" out. A issue in recent releases made it so the default was only made as a 1 year expiration from installation. We have since corrected that and the latest releases should once again be creating certs with longer expirations. However, a 1 year default expiration is actually the industry standard. However, I believe that is the primary reason we're seeing some of these issues today.

    With that said, it is highly recommended that customers use their own certs, and not the default certs. This is a more secure way to manage your environment, and would allow you to manage the expiration of the certs across various products outside of CSM.