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 (

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 Is a defect
Created by Guest
Created on Jan 8, 2018

Connect Direct Certificate Renewal is shown as successful though it is unsuccessful

When the license renewal of Connect:Direct certificate is unsuccessful, no message is shown on GUI or logs. When IBM support is contacted, they replied that the correct logs will be captured in debug mode. As an interim measure, IBM support asked to check for the following statement in cms.log :
CONF014I Update config definition : G3SSPEngine_KeyStore succeeded.
If the above message is not found in the log, IBM support asked to enable the debug mode and renew the certificate again.

We request to fix this bug in the upcoming release to clearly show an error in GUI whenever the renewal is unsuccessful. Based on the message on GUI, we can open the logs and check for the exact error. Without any notification in GUI, the renewal is generally considered as successful. When this error occurs, no further action should be invoked. Currently, even though the error occurs, the renewal process continues normally as if nothing happened.

The product also need to ensure that the old certificate is deleted and the new certificate is injected before confirming on the GUI that the certificate renewal is successful. Currently, IBM support is unable to confirm the root cause. They say it may be due to a couple of scenarios :
1) The import failed. This would pop up a message on the screen and the user would have to click "OK" to continue.
2) The import worked, but when the certificate was imported, the user did not select the new keycert in the netmap for the pnode and it was still pointing to the old certificate, not the new one. So when the old one expired on the 27'th, the transfers started to fail.
DeveloperWorks ID DW_ID80371
Link to original RFE