webhook notification channel missing Bearer
search cancel

webhook notification channel missing Bearer

book

Article ID: 386761

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

For the demo server, Created a webhook channel receiver and UI display to test out the webhook notification channel.

So far, connecting to it works. But colleagues asked how to troubleshoot troubleshoot it, how to ensure it went through etc.

This is a required feature for current SaaS deployments, as currently only devs can check what went wrong.

Note: This webhook channel receiver notifies a Bug to support where the Token authentication header has been changed in removing the "Bearer" keyword.


The change happened with the latest SaaS update to:

About DX Operational Observability Release: 25.1.1 (Build: 159)
Tenant Status: Enterprise
DX App Experience Analytics: 25.1.1.7
Enterprise Manager: 25.1.1.25

 

Resolution

Internal test results:

Entered "Bearer <rtoken>" for Token earlier, that's why the Bearer part is seen.

Just changed it to just "<token>", and tested from 24.11 and 25.1.1 (SaaS).Seeing the same Authorization header without "Bearer". 

Expecting this as before:

[Authorization] => blabla.token


If wanting a Bearer part,  include it in the Token.