1、ES在老版本中没有用户认证,升级ES的开销又特别大,尤其是跨大版本的时候,语法有变了,所以好多小项目都选择了破解X-pack为ES加密。
2、X-pack的安装我们在这里略过,百度一大堆。。。。。接下来我们已经对es添加了用户认证
3、我们连接Es的时候,需要提供用户认证。
这个时候我们使用之前demo连接的时候就会报错啦。
{"error":{"root_cause":[{"type":"security_exception","reason":"missing authentication token for REST request [/]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}}],"type":"security_exception","reason":"missing authentication token for REST request [/]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}},"status":401}
1、数据资产对于公司来说是一笔巨大的财富,怎么能随便的让别人拿到,就算添加防火墙,你们的渗透测试也过不了
2、添加密码有效保护信息,还有redis的连接,一般小项目都不加密码,给后期的维护还有不少的麻烦
1、RestClient的改造,找到RestClient的创建代码,改造如下
final CredentialsProvider credentialsProvider = new BasicCredentialsProvider();
credentialsProvider.setCredentials(AuthScope.ANY,
new UsernamePasswordCredentials("elastic", "changeme"));
//callback中添加用户信息
RestClient restClient = RestClient.builder(
httpHostList.toArray(new HttpHost[httpHostList.size()])
).setHttpClientConfigCallback(
new RestClientBuilder.HttpClientConfigCallback() {
@Override
public HttpAsyncClientBuilder customizeHttpClient(HttpAsyncClientBuilder httpAsyncClientBuilder) {
return httpAsyncClientBuilder.setDefaultCredentialsProvider(credentialsProvider);
}
}
).build();
2、客户端改造
1、之前的客户端连接PreBuiltTransportClient 必须替换为X-pack自己的连接包
添加maven依赖
org.elasticsearch.client
x-pack-transport
5.2.2
org.elasticsearch
elasticsearch
2、修改之前PreBuiltTransportClient 的连接方式
Settings settings = Settings.builder()
.put("cluster.name", clusterName)
.put("xpack.security.user", "elastic:changeme")
.build();
//注释掉之前的客户端创建方式
//TransportClient client = new PreBuiltTransportClient(settings);
//使用如下方式
TransportClient client = new PreBuiltXPackTransportClient(settings);
final CredentialsProvider credentialsProvider = new BasicCredentialsProvider();
credentialsProvider.setCredentials(AuthScope.ANY,
new UsernamePasswordCredentials("elastic", "changeme"));
这两种方法在ES5.6.16,都可以正常连接ES。其他客户端连接改造,后面文章介绍