- Search Guard and Elasticsearch version
SG - 6.4.2-23.2
ES - 6.4.2
- JVM version and operating system version
java version “1.8.0_162”
Java™ SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot™ 64-Bit Server VM (build 25.162-b12, mixed mode)
NAME=“Ubuntu”
VERSION=“18.04.1 LTS (Bionic Beaver)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 18.04.1 LTS”
VERSION_ID=“18.04”
- Search Guard configuration files
config.yml
···
--------------
ca:
root:
The distinguished name of this CA. You must specify a distinguished name.
dn: CN=root.ca.pipl.pro,OU=IL,O=Pipl,L=IL,C=IL,DC=pro
pkPassword: xxxxxxxx
file: root-ca.pem
intermediate:
dn: CN=signing.ca.pipl.pro,OU=IL,O=Pipl,L=IL,C=IL,DC=pro
pkPassword: xxxxxxxxx
file: intermediate-ca.pem
defaults:
validityDays: 3650
pkPassword: auto
httpsEnabled: true
verifyHostnames: true
resolveHostnames: true
nodes:
- name: xxxxxxx-001.xxxxx.pro
dn: CN=es-k8s-001.pipl.pro,OU=IL,O=xxxx,L=IL,C=IL,DC=pro
dns: xxxxxxx-001.xxxxxxl.pro
- name: xxxxxxxx-002.xxxxxxx.pro
dn: CN=xxxxxxx-002.xxxxxx.pro,OU=IL,O=xxxxx,L=IL,C=IL,DC=pro
dns: xxxxxx-002.xxxxx.pro
- name: node3
dn: CN=xxxxxxx-002.xxxxx.pro,OU=IL,O=xxxxxx,L=IL,C=IL,DC=pro
dns: xxxxxxx-003.xxxxxx.pro
clients:
- name: spock
dn: CN=spock.xxxxxx.pro,OU=IL,O=xxxxxxx,L=IL,C=IL,DC=pro
- name: kirk
dn: CN=kirk.xxxxxx.pro,OU=IL,O=xxxxxx,L=IL,C=IL,DC=pro
admin: true
elasticsearch.yml
----------------------
searchguard.ssl.transport.pemcert_filepath: xxxxxxx-001.xxxxxxx.pro.pem
searchguard.ssl.transport.pemkey_filepath: xxxxxxx-001.xxxxxx.pro.key
searchguard.ssl.transport.pemkey_password: xxxxxxxxx
searchguard.ssl.transport.pemtrustedcas_filepath: root-ca.pem
searchguard.ssl.transport.enforce_hostname_verification: true
searchguard.ssl.transport.resolve_hostname: true
searchguard.ssl.http.enabled: false
searchguard.ssl.http.pemcert_filepath: xxxxxxxx-001.xxxxxxx.pro_http.pem
searchguard.ssl.http.pemkey_filepath: xxxxxx.xxxxxx.pro_http.key
searchguard.ssl.http.pemkey_password: LUIL6RfUFAQL
searchguard.ssl.http.pemtrustedcas_filepath: root-ca.pem
searchguard.nodes_dn:
-
CN=es-k8s-001.pipl.pro,OU=IL,O=xxxxx,L=IL,C=IL,DC=pro
-
CN=es-k8s-002.pipl.pro,OU=IL,O=xxxxx,L=IL,C=IL,DC=pro
-
CN=es-k8s-002.pipl.pro,OU=IL,O=xxxxx,L=IL,C=IL,DC=pro
searchguard.authcz.admin_dn:
- CN=kirk.pipl.pro,OU=IL,O=xxxxxx,L=IL,C=IL,DC=pro
“elasticsearch.yml” 195L, 6423C
- Elasticsearch log messages on debug level
[2018-11-29T10:29:15,389][ERROR][c.f.s.a.BackendRegistry ] Not yet initialized (you may need to run sgadmin)
**AFTER INITIALIZING **
----------------------
WARNING: JAVA_HOME not set, will use /usr/bin/java
Search Guard Admin v6
Will connect to localhost:9300 … done
ERR: An unexpected IllegalStateException occured: failed to load plugin class [com.floragunn.searchguard.SearchGuardPlugin]
Trace:
- Other installed Elasticsearch or Kibana plugins, if any
Kibana
Hello, I’m trying to work with search-guard for our data encryption.
I followed all the necessary steps of Installation from your page, and steps of generating the certificates from this page, by creating the root ca and intermediate ca - Production-ready TLS certificates for Elasticsearch | Search Guard
When trying to make the following step ( initialize search-guard) - ./sgadmin.sh -key ./kirk-key.pem -keypass 8Faq7qPtP1DH -cert ./kirk.pem -cacert ./root-ca.pem …
I receive the following error -
WARNING: JAVA_HOME not set, will use /usr/bin/java
Search Guard Admin v6
Will connect to localhost:9300 … done
ERR: An unexpected IllegalStateException occured: failed to load plugin class [com.floragunn.searchguard.SearchGuardPlugin]
Trace:
Could you please assist?
Thanks!
Aleksei