oscerd opened a new pull request, #2037: URL: https://github.com/apache/camel-spring-boot/pull/2037
## Summary This is a follow-up of [CAMEL-25568](https://issues.apache.org/jira/browse/CAMEL-25568) (apache/camel#27718), suggested in its review. camel-oauth now reads the bearer token from the HTTP request of the message, rather than from the message headers, which also hold the query and form parameters. camel-oauth does not depend on this starter, so it recognises `org.apache.camel.component.platform.http.springboot.PlatformHttpMessage` by class name and reads the request from its `getRequest()`. This adds `SpringBootPlatformHttpOAuthBearerTokenTest`. It runs `OAuthBearerTokenProcessor` behind the real Spring Boot platform-http consumer, with a stub identity provider, and checks that: * the token is read from the `Authorization` header; * it is not read from a form parameter or a query parameter of the same name; * the request is still found when the route removes the `Camel*` headers first. If `PlatformHttpMessage` is renamed, or no longer gives the request, the form-parameter cases fail. I checked this by running the test against a camel-oauth build whose class name match was changed: 2 failures, `Expected status code <401> but was <200>`. `camel-oauth` is added as a test dependency of `camel-platform-http-starter`. The test registers an `OAuthFactory` bean, because without one camel-oauth looks for the Vert.x platform-http router, whose class is not on this classpath. This needs a camel `4.23.0-SNAPSHOT` that contains apache/camel#27718; the Apache snapshots have it since 2026-10-14. `mvn -Psourcecheck verify` passes. _Claude Code on behalf of oscerd_ 🤖 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]
