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 Planned for future release
Categories APIs & SDKs
Created by Guest
Created on Apr 8, 2022

CDWS - certificate-based authentication - CLIENT certificate differentiation

We use standard connection path for certificate-based authentication:

CLIENT (for example curl command) -> CDWS (CD Web Services) -> CD (Connect Direct)

Let's assume that:

  • CLIENT uses client certificate with CNAME=cert1

  • CDWS server uses certificate with CNAME=cert2

  • CD server uses certificate with CNAME=cert3

For more clarity, let's assume, that:

  • All certificates (cert1, cert2, cert3) have the same issuer and use the same trusted CAs chain.

PROBLEM: No matter which certificate we use on the CLIENT's side (and authorize it in application.properties in CDWS), always we are connecting to CD using CDWS server's certificate. So no matter if on CLIENT we use CNAME=cert1 or CNAME=cert999, then it will be always connecting to the CD using CDWS certificate CNAME=cert2.

This means:

  • we can connect to CD only as one "user", the one which matches the CDWS certificate CNAME, however we need to connect to CD using multiple "users" that are equal to CLIENT's certificate CNAME.

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

Currently software does not distinguish the CLIENTs. Clients may use various certs and this fact should be distinguished.

This enhancement will allow to connect to CD as the user which matches the CNAME of CLIENT's certificate.

  • Admin
    Chris Sanders
    Aug 19, 2022

    Thank you for opening this enhancement request with IBM. I have reviewed it with my team and we believe that more closely tying certificates from the client connection to the C:D server itself is a valuable enhancement. There are some technical challenges with your specific certificate pass-through request, but we do intend to deliver an integrated REST API option moving forward. I believe this will meet your needs so I'm accepting this request as part of that activity.


    Sincerely,

    Chris Sanders

    Connect:Direct Product Manager