IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.
  • Guest
  • Jan 8 2018
  • Is a defect
DeveloperWorks ID DW_ID80371
Link to original RFE

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.