Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Mar 7, 2022

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

As defined here: :

"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