[feature] Webhook target should support Authorization mechanism

[harshavardhana]

Expected Behavior

Support Authorization header bearer token to be set for all event notifications.

Current Behavior

All requests to webhook are currently insecure or do have a way to validate the incoming request.

Possible Solution

For example looking for a following change

  "webhook": {
                        "1": {
                                "enable": false,
                                "authorization": "xxxxxxxxxx",
                                "endpoint": "https://requestb.in/1cxubuy1"
                        }
                },

Steps to Reproduce (for bugs)

Just follow the bucket notification guide on how to setup webhook notification and setup an insecure webhook endpoint.

Context

Security, avoiding lower room for attack radius etc.

Your Environment

Current master

[nap]

Anyone working on this? Are you accepting contributions?

[balamurugana]

@nap contributions are welcome. As there is a significant amount change in notification system, you could contribute to the PR #5294

[harshavardhana]

@nap contributions are welcome. As there is a significant amount change in notification system, you could contribute to the PR #5294

@nap will you be able to contribute?

[nap]

I don't think so.

[harshavardhana]

Taking this as part of the config changes..