Skip to content
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

Jump to bottom

Update to Vert.x 4.5.4 and Netty 4.1.107 #39001

Merged
merged 5 commits into from
Mar 5, 2024
Merged

Update to Vert.x 4.5.4 and Netty 4.1.107 #39001

merged 5 commits into from
Mar 5, 2024

Commits on Mar 1, 2024

  1. Update to Vert.x 4.5.4 and Netty 4.1.107 

    This update brings significant changes affecting extensions utilizing a (Vert.x) TCP client. With Vert.x version 4.5.4, establishing TLS connections now mandates the use of hostname verification algorithms. This requirement impacts various components including Reactive SQL clients, Redis, RabbitMQ, MQTT, among others.

Previously, if not explicitly specified by the protocol, the verification algorithm defaulted to "". This setting essentially skipped the verification process. However, with the new version, explicit configuration is necessary. Consequently, each extension has been adjusted to utilize the most appropriate verification algorithm.

It's important to note that these modifications may potentially disrupt existing applications. In such cases, referring to the documentation of the specific extension or component is recommended for proper configuration of the hostname verification algorithm.
    @cescoffier
    cescoffier committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    ee8b09a View commit details
    Browse the repository at this point in the history

  2. Update the Mutiny bindings to use Vert.x 4.5.4.

    @cescoffier
    cescoffier committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    11824c7 View commit details
    Browse the repository at this point in the history

  3. Change TLS Hostname Verifier in Reactive SQL Client default value (do… 

    … not break)

The update to Vert.x 4.5.4 necessitates adjustments in extensions leveraging the Vert.x TCP client, notably impacting reactive SQL clients. TLS connections now require explicit configuration of hostname verification algorithms.

Previously, in the absence of explicit specification by the protocol, the verification algorithm defaulted to "". Although this default remains unchanged in this commit, a MicroProfile Config limitation (eclipse/microprofile-config#446) highlights that "" is not a valid value in the Quarkus configuration. Consequently, "NONE" has been adopted as an alternative. This enables users to explicitly set the hostname verification algorithm to "NONE" to bypass the verification process.
    @cescoffier
    cescoffier committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    db68332 View commit details
    Browse the repository at this point in the history

  4. Update SmallRye Reactive Messaging to 4.18.0 

    This update addresses the breaking changes introduced by Vert.x 4.5.4 for MQTT and RabbitMQ integration regarding hostname verification.

To maintain backward compatibility, hostname verification is still disabled by default. However, to provide users with flexibility and security options, this version introduces connector options to activate hostname verification without using the programmatic customization.
    @cescoffier
    cescoffier committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    6e4dee7 View commit details
    Browse the repository at this point in the history

  5. Update Quarkus HTTP to 5.2.0.Final 

    This version aligns the Vert.x and Netty versions.
    @cescoffier
    cescoffier committed Mar 1, 2024
    Configuration menu
    Copy the full SHA
    261d756 View commit details
    Browse the repository at this point in the history