-
Notifications
You must be signed in to change notification settings - Fork 611
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
[Bug] Regression starting with 4.1.17 in the migration tool with certificate validation #2342
Comments
thanks for this report @andres-tw , this will be fixed in 4.1.19 |
@andres-tw create a configuration file
Then add the parameter |
@To-om Ah yes, sorry forgot to include the hive3 config. For all tests it's been configured as follows:
Tested now again, with only the trustStore configuration like in your example. |
@To-om Anything else I can test or your working on it? |
You can now configure http client by adding
|
So the new config option did not help. Fails with the same error message on both 4.19.1-1 and 5.0.2 docker images. Tried adding that config option both together with a truststore and without. I also tried configuring the trust store debugging, but that did not produce any extra logs to help me in debugging this further. Could it somehow be related to the fact that I'm trying to do the migration from a docker container? |
There is a typo in the last commit. The
This will be fixed in the next release. |
Request Type
Bug
Work Environment
Problem Description
Starting with version 4.1.17 when running the migration tool in a docker container initialisation of the migration fails with
PKIX path building failed
. Exactly the same configs work for starting the migration in 4.1.16-1.Steps to Reproduce
docker pull thehiveproject/thehive4:4.1.17-1
docker run -it --entrypoint /bin/bash -v "/opt/app/thehive/hive3.conf:/etc/thehive/hive3.conf:rw" -v "/opt/app/thehive/application.conf:/etc/thehive/application.conf:rw" -v "/opt/app/thehive/es.jks:/etc/thehive/es.jks:rw" --network host docker.tw.ee/tw-secops-thehive
./bin/migrate -d --output /etc/thehive/application.conf --main-organisation ORG_NAME --input /etc/thehive/hive3.conf
Possible Solutions
Not a solution, but a workaround might be to enable
index.search.elasticsearch.ssl.allow-self-signed-certificates
for migration connections somehow.Complementary information
Full stack trace:
The text was updated successfully, but these errors were encountered: