davsclaus opened a new pull request, #30365: URL: https://github.com/apache/camel/pull/30365
[CAMEL-27222](https://issues.apache.org/jira/browse/CAMEL-27222) ## What changed After Camel has checked the credential of a request, the `Authorization` header is removed from the message. The OAuth bearer token validation of these components already does this since 4.21. - **camel-platform-http-main:** server authentication with `basicPropertiesFile` or JWT, for paths under `authenticationPath`. - In `VertxPlatformHttpServer`, a small handler after each authentication handler marks the request. - The consumer then removes the header from the Camel message, in the same place where the endpoint `securityHandler` path already removes it. - The Vert.x request itself is left as it is. - **camel-netty-http:** basic authentication with `securityConfiguration`, for restricted resources. `CamelHttpAuthentication=Basic` is still set. - **camel-undertow:** requests authenticated by an `UndertowSecurityProvider`. The header is removed before the provider adds its own headers, so those still reach the route. - Requests that Camel does not check keep the header. - There is no opt-out option, as for the OAuth paths. A route that calls a backend sets the backend credentials on its producer. - Docs: a short paragraph on the platform-http-main, netty-http and undertow pages. ## Upgrade note New 4.24 upgrade-guide entry. ## Tests New tests: - camel-platform-http-vertx: basic and JWT, plus an unprotected path that keeps the header; - camel-platform-http-main: basic and JWT through the `camel.server.*` options; - camel-netty-http: `NettyHttpBasicAuthTest` and `NettyHttpBasicAuthConstraintMapperTest`; - camel-undertow: `SecurityProviderTest`. Each fails without the change. The full unit tests of the four modules pass: vertx 176, main 52, netty-http 383, undertow 297. _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]
