Integration

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

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 a notification 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.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to ideasibm@us.ibm.com for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Sep 2, 2021

Add subject validation option to Crypto Validation Credentials

When setting up communication over insecure channels (i.e. over Internet) it is required to narrow down list of clients that might connect to DataPower. This selection should be based on what is contained within Subject of client's certificate. Specification of what is allowed or denied access should be performed based on regular expression.

Idea Priority High
Why is it useful?

When securing communication between Remote Gateway and API Connect v10 Reserved Instance using MTLS customers will be able to specify subject of the client that's connecting to Gateway and allow only API Management subsystem to connect.

Customers might have policies that would require them to use specific CA, which is used to sign certificates company-wide, allowing attacks from insiders.

For particular customer that I worked with, it subject validation would prevent setup of Certificate Pinning, which is considered a bad practice.

Who would benefit from this IDEA? API Connect Reserved Instance customers with Remote Gateways