Skip to content

Feature : Allow additional headers to be passed to Schema Registry during http/s calls #793

Description

@dastokes273

Problem
Confluent Kafka Schema Registry supports authentication via OAuth. To support this a number of additional headers are required on the http client requests.

Solution
Ability to configure the Schema Registry Extension Provider with an arbitrary list of http headers to be passed on the client.

Alternatives
Full OAuth client authentication http client. This would be more effort, where as, is quite simple to set an Authorisation header with an OAuth bearer token, and any other headers that could be needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions