davsclaus opened a new pull request, #3245: URL: https://github.com/apache/camel-kamelets/pull/3245
Fixes #3244. `http-sink` sent an `Authorization` or `Proxy-Authorization` header that was already on the message, so behind `webhook-source` the credential of the caller went on to the target service, and with a login configured on the Kamelet the header of the message was sent instead of that login. ## Changes - `http-sink` removes `Authorization` and `Proxy-Authorization` from the message before the call, next to the headers it already removes (`CamelHttpUri`, ...). The login comes only from `authUsername`/`authPassword`, `authBearerToken` or the OAuth 2 options. - The description says so, and points to the `http` component for a token that differs for each message. ## Tests - `HttpSinkAuthorizationTest` runs `http-sink` against a local server with both headers on the message: without a login nothing is sent, and with a preemptive Basic login the configured login is sent. Both fail on `main` (the server gets `Bearer caller-token`). - `./mvnw clean install` passes. ## Upgrade A flow that set `Authorization` before `http-sink` on purpose now uses the login options, or the `http` component. To be added to the upgrade notes (#3190). _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
