Open zentavr opened 6 months ago
Seems like I'd found the issue: the DN in the certificates was in the reverse order:
(.venv) zentavr-m2:.self-signed zentavr$ openssl x509 -subject -nameopt RFC2253 -noout -in node.pem
subject=CN=*.wazuh-indexer,O=Company,L=California,C=US
(.venv) zentavr-m2:.self-signed zentavr$ openssl x509 -subject -nameopt RFC2253 -noout -in ../node.pem
subject=C=US,L=California,O=TI,CN=*.wazuh-indexer
(.venv) zentavr-m2:.self-signed zentavr$ openssl x509 -subject -nameopt RFC2253 -noout -in admin.pem
subject=CN=admin,O=Company,L=California,C=US
(.venv) zentavr-m2:.self-signed zentavr$ openssl x509 -subject -nameopt RFC2253 -noout -in ../admin.pem
So my opensearch.yml
looks like:
plugins.security.authcz.admin_dn:
# openssl x509 -subject -nameopt RFC2253 -noout -in node.pem
- 'CN=admin,O=TI,L=California,C=US'
- 'C=US,L=California,O=TI,CN=admin'
plugins.security.nodes_dn:
# openssl x509 -subject -nameopt RFC2253 -noout -in admin.pem
- 'CN=*.wazuh-indexer,O=TI,L=California,C=US'
- 'C=US,L=California,O=TI,CN=*.wazuh-indexer'
- 'CN=*.wazuh-indexer,O=TI,L=California,C=US' - 'C=US,L=California,O=TI,CN=*.wazuh-indexer'
Thank you. I encountered the same issue!
I'm trying to install wazuh with this YAMLs into my Kubernetes and have an error
Transport client authentication no longer supported
from wazuh-indexer component.Logs from the slave node:
Logs from the master node: