Skip to Main Content
Cloud Management and AIOps

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

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, 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 Under review
Created by Guest
Created on Mar 7, 2022

Messagebus Probe WebHook should respond with WWW-Authenticate entry in header for authentication

As defined here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication : "RFC 7235 defines the HTTP authentication framework, which can be used by a server to challenge a client request, and by a client to provide authentication information. The challenge and response flow works like this: 1. The server responds to a client with a 401 (Unauthorized) response status and provides information on how to authorize with a WWW-Authenticate response header containing at least one challenge. 2. A client that wants to authenticate itself with the server can then do so by including an Authorization request header with the credentials. 3. Usually a client will present a password prompt to the user and will then issue the request including the correct Authorization header." So, when implementing a workflow that interacts with MessageBus Probe WebHook, because the probe is acting as a server, one would expect to receive the challenge (WWW-Authenticate entry in header) in the response. For more details about the response headers expected to define the authentication method are described in that document, in section "WWW-Authenticate and Proxy-Authenticate headers" - in our case, we are interested in the WWW-Authenticate header, more specifically with = Basic. It would be nice to be able to configure the value for realm via the properties file, but that is not really required. Currently, we are receiving the 401 response, but we are missing the WWW-Authenticate response header from step 1 above. Because we do not have that header entry, the flow of the authentication is broken and we cannot move to Step 2.
Idea priority Low