Skip to content

Add ConnectionFactory#disableHostnameVerification - #2187

Draft
acogoluegnes wants to merge 1 commit into
mainfrom
conn-fact-disable-hostname-verification
Draft

acogoluegnes wants to merge 1 commit into
mainfrom
conn-fact-disable-hostname-verification

Conversation

@acogoluegnes

Copy link
Copy Markdown
Contributor

Server hostname verification is enabled by default for TLS connections with blocking IO. It is no longer removed when the socket configurator is replaced with ConnectionFactory#setSocketConfigurator. Applications that replaced the socket configurator to skip hostname verification must now call disableHostnameVerification after setting up TLS.

Disabling hostname verification is not recommended because it is not safe. The server certificate is still validated against the trust store, but not against the broker host name. Prefer using a server certificate that matches the host name used to connect to the broker.

Server hostname verification is enabled by default for TLS connections
with blocking IO. It is no longer removed when the socket configurator
is replaced with ConnectionFactory#setSocketConfigurator. Applications
that replaced the socket configurator to skip hostname verification
must now call disableHostnameVerification after setting up TLS.

Disabling hostname verification is not recommended because it is not
safe. The server certificate is still validated against the trust
store, but not against the broker host name. Prefer using a server
certificate that matches the host name used to connect to the broker.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant