davsclaus opened a new issue, #3257: URL: https://github.com/apache/camel-kamelets/issues/3257
`http-sink` no longer sends the `Authorization` or `Proxy-Authorization` header of the incoming message (#3244, #3245): the login comes only from its options. Three other Kamelets that send HTTP requests still send those headers on, as checked with `camel run` and a local server that logs the `Authorization` header: | Kamelet | Sends the incoming `Authorization` on | Login options | |---|---|---| | `rest-openapi-sink` | yes | none | | `ogcapi-features-action` | yes | none | | `azure-functions-sink` | yes (also an incoming `x-functions-key` when `key` is not set) | `key` | For example, behind `webhook-source`, the token of the caller of the webhook goes to the API. ## Proposal - All three remove `Authorization` and `Proxy-Authorization` from the incoming message first, as `http-sink` does. `azure-functions-sink` also removes an incoming `x-functions-key`. - `ogcapi-features-action` calls the `http` component directly, so it gets the login options of `http-sink`: `authMethod`, `authUsername`, `authPassword`, `authBearerToken`, `authenticationPreemptive` and the `oauth2*` options. - `rest-openapi-sink` gets `authUsername` and `authPassword` (passed on to the `http` endpoint; sent after the service answers 401), and `authBearerToken`, which the Kamelet sends itself as a Bearer token and removes from the message after the call. The other login options of `http-sink` do not work through `rest-openapi` today: CAMEL-27234. This is the "authentication for `rest-openapi-sink` and `ogcapi-features-action`" item that #3170 left for later. Found on the way: with OAuth2, a token endpoint on the same host and port as the API makes the call fail with `Connection pool shut down` (CAMEL-27233). That affects `http-sink` and `http-source` too. _Claude Code on behalf of Claus Ibsen_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
