Skip to content

Conversation

@yanivbh1
Copy link

Adding ability to add authorization header
to support JWT-type authentication which is highly common pattern and will enable variety of use cases with debezium and HTTP sink

@jpechane
Copy link
Contributor

@yanivbh1 Could you please create a Jira issue for this?
Also I beleive the problem needs to be handled in more general way

  • Debezium Server now supports sinks the ability to use headers passed - see Kafka sink for implementation. The code sould support it
  • Instead ofconfiguring http headers one by one there should be a set header.* config options that will take the last part and addsuch header to request. This will enable user configure any header
  • In case of coflict of two items above the incoming header takes precedence and overwirtes the one statically configured

@gunnarmorling
Copy link
Member

@jpechane, is this one still relevant? Seems it actually has been addressed already?

@jpechane
Copy link
Contributor

@gunnarmorling I think it still is. So far you can either use jwt authentication or pass Kafka Connect headers. But there is no way how to configure an HTTP header statically in the Debezium Server config.

@Naros
Copy link
Member

Naros commented Jan 6, 2026

❌ Developer Certificate of Origin (DCO) check failed.

Hi @yanivbh1, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

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.

4 participants