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.

Certificate-based authentication support for Connect:Direct RESTful API

Connect:Direct Java API supports certificate-based authentication. IBM Sterling Control Center also can use certificate-based authentication to connect and manage Connect:Direct settings. However latest version of RESTful API supports only user/password authentication. Please add certificate-based authentication for Connect:Direct RESTful API.

  • Guest
  • Sep 26 2018
  • Delivered
What is your industry? Banking
How will this idea be used?

Password/user authentication forces to use one of those solutions: common domain account (AD, LDAP, etc.) with password or maintain separate (e.g. local) users/passwords on each and every server with installed Connect:Direct. From security, compliance and operational standpoint both solutions are not ideal. RESTful API should support at least the same methods of authentication as other tools like Connect:Direct Java API or IBM Sterling Control Center.

  • Admin
    Chris Sanders commented
    19 Aug, 2019 12:09pm

    Thank you for your patience as we worked on this enhancement. I'm pleased to announce that this has been provided in C:D Web Services Fix Pack 3 which is available on IBM's Fix Central website. Please download and apply this maintenance which will allow you to start leveraging certificates to authenticate REST API connections.


    Chris Sanders

    Connect:Direct Offering Manager

  • Admin
    Chris Sanders commented
    2 Nov, 2018 03:11pm

    Thank you for opening this enhancement request with IBM.  I have reviewed it with my team and believe this would be a valuable enhancement to Connect:Direct.  I will accept this request as an uncommitted candidate and we will look to add it to the C:D roadmap moving forward.


    Chris Sanders

    Connect:Direct Offering Manager

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.