Which use case/requirement will be addressed by the proposed feature?

The HTTP client does not currently work with endpoints that require authorization such as JSON Web Tokens. 

Implementation ideas (optional)

JWT authorization has two steps: (1) authorize against the endpoint and receive a token and (2) pass the token in the header in requests to the endpoint.  JWT authorizations expire, however, and need to be periodically renewed.   Simply passing in tokens from a prior authorization session will only work for a short time – this can be problematic for a long-running service.

Should the HTTP client take a username and password in the configuration file and handle (re-)authorization automatically?  Or do best practices suggest a different approach – e.g., perform authorization outside of Debezium Server, pass the resulting token to Debezium Server through the config file, and just restart the entire container when the authorization expires,?