From 490962d08b4a6dd3f2a45056a79e87357fabb955 Mon Sep 17 00:00:00 2001 From: praveenkrishna Date: Mon, 11 Dec 2023 12:26:49 +0530 Subject: [PATCH] Use correct HostnameVerifier when verify-hostnames set to true Previously we were using `NoopHostnameVerifier` which turns off hostname verification, if the HostnameVerifier is not set it uses `DefaultHostnameVerifier` which performs hostname verification --- .../trino/plugin/elasticsearch/client/ElasticsearchClient.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugin/trino-elasticsearch/src/main/java/io/trino/plugin/elasticsearch/client/ElasticsearchClient.java b/plugin/trino-elasticsearch/src/main/java/io/trino/plugin/elasticsearch/client/ElasticsearchClient.java index f23bb90862ae..3fcea05054f1 100644 --- a/plugin/trino-elasticsearch/src/main/java/io/trino/plugin/elasticsearch/client/ElasticsearchClient.java +++ b/plugin/trino-elasticsearch/src/main/java/io/trino/plugin/elasticsearch/client/ElasticsearchClient.java @@ -225,7 +225,7 @@ private static BackpressureRestHighLevelClient createClient( buildSslContext(config.getKeystorePath(), config.getKeystorePassword(), config.getTrustStorePath(), config.getTruststorePassword()) .ifPresent(clientBuilder::setSSLContext); - if (config.isVerifyHostnames()) { + if (!config.isVerifyHostnames()) { clientBuilder.setSSLHostnameVerifier(NoopHostnameVerifier.INSTANCE); } }