Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Submitted
Created by Guest
Created on Aug 31, 2026

Enable CSPA600W certificate-expiry alerting to evaluate the certificate actively in use from the Secure Plus in-storage cache, not only the ACF2/RACF key ring.

Today, Connect:Direct Secure Plus certificate-expiry alerting (CSPA600W) evaluates the certificate installed in the RACF key ring. However, Connect:Direct runs off the certificate held in its in-storage Secure Plus cache until a Secure Plus Refresh (RF) is issued.

After a certificate renewal these two diverge: the key ring holds the new certificate (outside the CHECK.CERT.EXPIRE.WARN.DAYS window, so CSPA600W correctly goes silent), while the running node continues to use the older cached certificate that is near expiry (without secureplus refresh). This creates a blind spot — no expiry warning is generated for the certificate actually in use, during the exact window when TLS handshake failures occur.

Requested enhancement:

  1. Base CSPA600W (or an equivalent check) on the certificate currently in the Secure Plus in-storage cache.

  2. Generate an alert when the cached certificate diverges from the key ring certificate (a "refresh required" condition).

  3. Provide a supported command/API to query the expiry date of the certificate currently held in the Secure Plus cache, so external automation can validate the active certificate.

What is your industry? Banking
How will this idea be used?

We renew Secure Plus certificates during scheduled change windows across many Connect:Direct nodes. This enhancement would alert us whenever a node's active (cached) certificate is approaching expiry — including the post-renewal, pre-refresh window — so we can act before TLS handshakes fail. It lets us monitor the certificate Connect:Direct is truly using, rather than only the key ring copy, and integrate that state into our existing automation.