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 135c96db89ec CAMEL-27228, CAMEL-27229: Upgrade guide notes for 4.22.3 
and 4.18.6 - camel-vertx-http https:// addresses and camel-ftp ftps trust store 
(#30384)
135c96db89ec is described below

commit 135c96db89ecee01e3e78a4b6f35430effa83400
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Nov 19 14:52:56 2026 +0100

    CAMEL-27228, CAMEL-27229: Upgrade guide notes for 4.22.3 and 4.18.6 - 
camel-vertx-http https:// addresses and camel-ftp ftps trust store (#30384)
    
    The upgrade notes of the backports of CAMEL-27228 (#30372) and CAMEL-27229
    (#30373), in camel-4x-upgrade-guide-4_22.adoc (4.22.2 to 4.22.3) and
    camel-4x-upgrade-guide-4_18.adoc (4.18.5 to 4.18.6):
    - camel-vertx-http: an https:// address always uses TLS. On 4.18.x this is 
the
      addresses with a port, because addresses without a port already used TLS
      there.
    - camel-ftp: an ftps endpoint without trust settings checks the server
      certificate against the JVM trust store.
    
    Docs only.
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc    | 25 ++++++++++++++++++++++
 .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc    | 24 +++++++++++++++++++++
 2 files changed, 49 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 435965958c58..bf9b5b1338eb 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
@@ -1098,6 +1098,31 @@ To have a placeholder resolved, keep it in the uri 
written in the route rather t
 `recipientList`, `routingSlip` and `dynamicRouter` are unchanged. Their 
recipient is computed entirely at runtime and may
 carry a placeholder that comes from configuration, so they continue to resolve 
`+{{...}}+` in the computed recipient.
 
+=== camel-ftp - ftps checks the server certificate against the JVM trust store 
when no trust store is configured
+
+An `ftps` endpoint configured with neither `sslContextParameters` nor the 
`ftpClient.trustStore.` options now checks the
+certificate of the server against the default trust store of the JVM (the 
`cacerts` file of the JDK, or the trust
+store set with the `javax.net.ssl.trustStore` system property). Before, such 
an endpoint accepted any server
+certificate within its validity dates, without checking who signed it.
+
+A server certificate signed by a public certificate authority works as before. 
For an FTPS server with a self-signed
+certificate, or a certificate signed by your own certificate authority, the 
connection now fails in the TLS handshake:
+put that certificate (or the certificate of the authority) in a trust store, 
and configure it with the
+`ftpClient.trustStore.file`, `ftpClient.trustStore.password` and 
`ftpClient.trustStore.type` options, or with
+`sslContextParameters`. A custom `ftpClient` keeps the trust manager it was 
created with. See
+xref:components::ftp-component.adoc#_ftps_component_default_trust_store[FTPS 
component default trust store].
+
+=== camel-vertx-http - an https:// address with a port always uses TLS
+
+A `vertx-http` endpoint with an `https://` address that has an explicit port 
(such as `https://host:8443/path`) now
+always calls it with TLS, also when no `sslContextParameters` is configured, 
and also through a proxy. The server
+certificate is then checked with the default trust store of the JVM, and the 
host name is verified. Before, such a
+request was sent without TLS unless TLS was turned on by 
`sslContextParameters`, global SSL settings or custom
+`WebClientOptions`. `https://` addresses without a port already used TLS.
+
+A route that called an `https://` address of a server that only speaks plain 
HTTP now fails; use an `http://` address
+for such a server. An `http://` address with `sslContextParameters` is not 
changed.
+
 === camel-redis - RedisAggregationRepository stores exchanges in Java 
serialization, read through a deserialization filter
 
 `RedisAggregationRepository` now stores the exchanges in its Redis hashes as 
Java serialization, with the correlation
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 a824b598d0d0..cd709ff6d149 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
@@ -1038,6 +1038,30 @@ is computed per message, this also applies to a 
`+++RAW($simple{env:MY_PASSWORD}
 use a property placeholder instead, such as 
`+toD("ftp:joe@${header.host}?password=RAW({{env:MY_PASSWORD}})")+`, which
 is resolved once when the route is created.
 
+=== camel-ftp - ftps checks the server certificate against the JVM trust store 
when no trust store is configured
+
+An `ftps` endpoint configured with neither `sslContextParameters` nor the 
`ftpClient.trustStore.` options now checks the
+certificate of the server against the default trust store of the JVM (the 
`cacerts` file of the JDK, or the trust
+store set with the `javax.net.ssl.trustStore` system property). Before, such 
an endpoint accepted any server
+certificate within its validity dates, without checking who signed it.
+
+A server certificate signed by a public certificate authority works as before. 
For an FTPS server with a self-signed
+certificate, or a certificate signed by your own certificate authority, the 
connection now fails in the TLS handshake:
+put that certificate (or the certificate of the authority) in a trust store, 
and configure it with the
+`ftpClient.trustStore.file`, `ftpClient.trustStore.password` and 
`ftpClient.trustStore.type` options, or with
+`sslContextParameters`. A custom `ftpClient` keeps the trust manager it was 
created with. See
+xref:components::ftp-component.adoc#_ftps_component_default_trust_store[FTPS 
component default trust store].
+
+=== camel-vertx-http - an https:// address always uses TLS
+
+A `vertx-http` endpoint with an `https://` address now always calls it with 
TLS, also when no `sslContextParameters`
+is configured. The server certificate is then checked with the default trust 
store of the JVM, and the host name is
+verified. Before, the request was sent without TLS unless TLS was turned on by 
`sslContextParameters`, global SSL
+settings or custom `WebClientOptions`.
+
+A route that called an `https://` address of a server that only speaks plain 
HTTP now fails; use an `http://` address
+for such a server. An `http://` address with `sslContextParameters` is not 
changed.
+
 === camel-redis - RedisAggregationRepository stores exchanges in Java 
serialization, read through a deserialization filter
 
 `RedisAggregationRepository` now stores the exchanges in its Redis hashes as 
Java serialization, with the correlation

Reply via email to