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 Delivered
Created by Guest
Created on Oct 5, 2020

BYO (Bring Your Own) Certificate with CRL checking

For "New Install" tasks - instead of using self-signed certificates, Control Center Director should allow to use user's certificate for the communication between Connect Direct server and Control Center Director.

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

Such feature would allow to replace communication based on self-signed CCD certificates with communication encrypted by certificate brought by user. Private key should not be shared nor included to the .zip/.tar bundle. The installer scripts (installCD.sh or installCDWindows.ps1) could take the certificate/key from the local file system on the Connect Direct server as an input to installCD.sh/installCDWindows.ps1 scripts.

Software should have an option to disable self-signed certificates communication - ideally not only by limiting the list of trusted certificates in the truststore but also by an explicit settings in the configuration.

If software at any stage verifies the certificate then it should have a CRL (certificate revocation list) checking mechanism implemented.

  • Admin
  • Admin
    Chris Sanders
    Reply
    |
    Oct 16, 2020

    Thank you for opening this enhancement request with us. I had a chance to review this with my team and we're in agreement that adding the ability to point to an externally generated certificate for new C:D deployments would be both valuable and technically feasible. We will accept this request and will look to add it to the roadmap moving forward.

    Sincerely,

    Chris Sanders

    Control Center Director Offering Manager