Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XPACK/Secure Elasticsearch Communications Support #5

Open
bionicspy opened this issue Dec 28, 2017 · 0 comments · May be fixed by #7
Open

XPACK/Secure Elasticsearch Communications Support #5

bionicspy opened this issue Dec 28, 2017 · 0 comments · May be fixed by #7

Comments

@bionicspy
Copy link

There is no default support for secure elasticsearch parameters communications such as XPACK protected cluster. (suspect others like SHIELD and SearchGaurd protected clusters will have similar requirements)

(Verified workaround on Elasticsearch 5.6.3 with XPACK enabled)
Suggest adding additional (or potentially optional) dependency (pip install certifi) and add line
import certifi
to import section of import_testssl.sh_csv_to_ES.py

Note: When using non-public CA for elasticsearch cluster, you must also append CA (and Intermediate, if required) to certifi cacert.pem chain.
cat root-ca.pem >> /usr/lib/python3.4/site-packages/certifi/cacert.pem
cat intermediate-ca.pem >> /usr/lib/python3.4/site-packages/certifi/cacert.pem
(Tested Python 3.4 on CentOS 7.4)

Enables (XPACK enabled cluster with encrypted communications and authentication)
./import_testssl.sh_csv_to_ES.py *.csv --elasticsearch https://username:[email protected]:9200

  • where username, has been granted write privileges to testssl-* indexes
@C0FFEEC0FFEE C0FFEEC0FFEE linked a pull request Oct 23, 2018 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant