Cameron Fitzwater created CAMEL-22645:
-----------------------------------------
Summary: http-component - oauth2BodyAuthentication not being
stipped out of URI
Key: CAMEL-22645
URL: https://issues.apache.org/jira/browse/CAMEL-22645
Project: Camel
Issue Type: Bug
Components: camel-http
Affects Versions: 4.14.0
Reporter: Cameron Fitzwater
The implementation of `oauth2BodyAuthentication` may be missing a step of
removing the parameter from the calls URI (it is being populated forward in the
URI – see example).
This is not the case with other oauth2* parameters (they are not included in
the URI).
e.g.,
- to:
uri: "\{{api.uri}}/api/v3/address"
parameters:
sslContextParameters: "#bean:sslContextParameters"
httpMethod: "GET"
bridgeEndpoint: true
skipControlHeaders: true
skipRequestHeaders: true
okStatusCodeRange: 200
# OAuth2 parameters
oauth2ClientId: "\{{api.consumer.key}}"
oauth2ClientSecret: "\{{api.consumer.secret}}"
oauth2TokenEndpoint: "\{{api.uri}}/oauth2/v3/token"
oauth2BodyAuthentication: true
oauth2Scope: "addresses"
Reviewing the DEBUG logs, it is sending the request with:
`GET /api/v3/address?oauth2BodyAuthentication=true&...`
Expected:
`GET /api/v3/address?...`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
