IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Workspace Cloud Pak for Data
Created by Guest
Created on Oct 29, 2020

Add HSTS config for root of WMLA Conductor

HSTS can be set for port 8443, 8543, and 8643 (webgui, rest api, ascd) but only at an "application root" level. If testing a port at the "server root" level, we don't see HSTS set. This gets flagged by vulnerability scanners, because the scanner doesn't know to go to the "application root." The RFCs describe this at a domain and port level, not sub-resource (application root) level, so this seems to be poor behavior. Please allow for configuring of HSTS at the server root level (domain:port) such that a request to "/" also returns HSTS, rather than only seeing this if we hit a specified application root path.