This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 48d703fe21f4 CAMEL-25638: camel-graphql - upgrade-guide notes for
4.22.2 and 4.18.6 (#27867)
48d703fe21f4 is described below
commit 48d703fe21f496660cede4efa071229a2c14f57f
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Oct 15 14:01:04 2026 +0200
CAMEL-25638: camel-graphql - upgrade-guide notes for 4.22.2 and 4.18.6
(#27867)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 9 +++++++++
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 14 ++++++++++++++
2 files changed, 23 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 62c767765737..22210e2210f0 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -44,6 +44,15 @@ user is now accepted only when one of their roles is equal
to one of those names
whitespace around each name and blank entries are ignored, and a value of `*`
still accepts any role. A roles value
that uses another separator, such as `admin;guest` or `admin guest`, must be
changed to `admin,guest`.
+=== camel-graphql - the credentials are only sent to the authority of httpUri
+
+The `accessToken` (with its `jwtAuthorizationType`) is now added to a request
only when the request goes to the
+scheme, host and port of `httpUri`, and the `username` and `password` are
registered for that authority only.
+Previously neither was bound to the authority of `httpUri`. A request to
another authority, including the same host
+with another scheme or port, is now sent without them. A route that needs to
authenticate to another authority must
+address it in `httpUri`. When `proxyHost` is set, the `username` and
`password` are no longer offered to the proxy when
+it asks for authentication.
+
=== camel-telegram - webhook requests are verified with a secret token
In webhook mode, Camel now registers the webhook with a secret token, which
Telegram sends in the
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index f8c3d4cff7d1..eaeb9b040803 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -110,6 +110,20 @@ user is now accepted only when one of their roles is equal
to one of those names
whitespace around each name and blank entries are ignored, and a value of `*`
still accepts any role. A roles value
that uses another separator, such as `admin;guest` or `admin guest`, must be
changed to `admin,guest`.
+=== camel-graphql - the credentials are only sent to the authority of httpUri
+
+The `accessToken` (with its `jwtAuthorizationType`) is now added to a request
only when the request goes to the
+scheme, host and port of `httpUri`, and the `username` and `password` are
registered for that authority only.
+Previously neither was bound to the authority of `httpUri`. A request to
another authority, including the same host
+with another scheme or port, is now sent without them. A route that needs to
authenticate to another authority must
+address it in `httpUri`. When `proxyHost` is set, the `username` and
`password` are no longer offered to the proxy when
+it asks for authentication.
+
+The producer also no longer takes the request URL from the `CamelHttpUri`,
`CamelHttpPath`, `CamelHttpQuery` and other
+camel-http control headers of the message. It did so since Camel 4.19, when
the component moved onto camel-http; the
+request now always goes to `httpUri`, as it did before. For the same reason
the `CamelHttpMethod` and
+`CamelHttpProtocolVersion` headers no longer apply, and the request is always
a POST.
+
=== camel-telegram - webhook requests are verified with a secret token
In webhook mode, Camel now registers the webhook with a secret token, which
Telegram sends in the
