Skip to content

SLK-110843 feat(webhook): add Authorization header support for webhook outputs#667

Merged
lionelresnik merged 2 commits intopostee-for-enterprisefrom
SLK-110843-webhook-auth-headers
Mar 17, 2026
Merged

SLK-110843 feat(webhook): add Authorization header support for webhook outputs#667
lionelresnik merged 2 commits intopostee-for-enterprisefrom
SLK-110843-webhook-auth-headers

Conversation

@lionelresnik
Copy link
Copy Markdown
Collaborator

@lionelresnik lionelresnik commented Mar 16, 2026

Summary

  • Added Headers field to WebhookOutput struct to support custom HTTP headers
  • Modified Send() method to use http.NewRequest instead of http.Post to allow setting headers
  • Updated buildWebhookOutput in router/builders.go to pass headers from OutputSettings
  • Added unit tests for webhook authentication scenarios (Bearer token, Basic auth)

Why

This enables webhook authentication (Bearer Token and Basic Authentication) for the Notifications pipeline, matching the existing Log Management webhook authentication feature (SLK-84531).

Test plan

  • Unit tests added for Bearer token auth
  • Unit tests added for Basic auth
  • Unit tests added for no auth (backward compatibility)
  • Unit tests added for error scenarios

Add Headers field to WebhookOutput struct and modify Send() to inject
custom headers into HTTP requests. This enables Bearer Token and Basic
Authentication for webhook notifications.

Resolves: SLK-110843
Made-with: Cursor
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@lionelresnik lionelresnik merged commit 46abf7a into postee-for-enterprise Mar 17, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants