Skip to content

CAMEL-25984: docs - upgrade guide entries for the camel-cometd CORS filter credentials in 4.22.3 and 4.18.6 #28504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davsclaus merged 1 commit into from
Oct 26, 2026
Merged

CAMEL-25984: docs - upgrade guide entries for the camel-cometd CORS filter credentials in 4.22.3 and 4.18.6 #28504

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -484,6 +484,14 @@ When configuring TLS through `SSLContextParameters` with a standalone `TrustMana
When both a `TrustManager` and a keystore are configured on `TrustManagersParameters`, the `TrustManager` is now used,
as with the other components that use `SSLContextParameters`; before, the keystore-based trust options were used.

=== camel-cometd - the CORS filter allows credentials only for listed origins

With `crossOriginFilterOn=true`, the CORS responses now include `Access-Control-Allow-Credentials: true` only when
`allowedOrigins` lists the origins explicitly, without any `*` or `null`. When `allowedOrigins` is not set, is `*`, or
has an entry with a wildcard such as `https://*` or an entry `null`, the origin is still allowed, but without
credentials. Previously credentials were allowed for every origin. A cross-origin client that sends cookies or other
credentials must have its origin listed in `allowedOrigins`.

== Upgrading from 4.18.4 to 4.18.5

=== camel-azure-eventhubs
Expand Down
8 changes: 8 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -291,6 +291,14 @@ When configuring TLS through `SSLContextParameters` with a standalone `TrustMana
When both a `TrustManager` and a keystore are configured on `TrustManagersParameters`, the `TrustManager` is now used,
as with the other components that use `SSLContextParameters`; before, the keystore-based trust options were used.

=== camel-cometd - the CORS filter allows credentials only for listed origins

With `crossOriginFilterOn=true`, the CORS responses now include `Access-Control-Allow-Credentials: true` only when
`allowedOrigins` lists the origins explicitly, without any `*` or `null`. When `allowedOrigins` is not set, is `*`, or
has an entry with a wildcard such as `https://*` or an entry `null`, the origin is still allowed, but without
credentials. Previously credentials were allowed for every origin. A cross-origin client that sends cookies or other
credentials must have its origin listed in `allowedOrigins`.

== Upgrading from 4.22.1 to 4.22.2

=== camel-lra - only an LRA hosted by the configured coordinator is joined
Expand Down
Loading