Closed jessesimpson36 closed 1 month ago
I mark this as code-freeze-candidate because the issue is not a regression as result of 8.6-alpha, it is simply a problem that exists both in 8.5 and 8.6
@hamza-m-masood informed me that the storepass
is not relevant to the stacktrace I received.
I will work on this issue
I will test this issue by setting up external bitnami elasticsearch, with ingress and self-signed cert. Then, I will connect using the camunda helm chart and the self-signed cert.
I can confirm that connecting to external elasticserach with self-signed certificates works with alpha chart
The team has decided to leave this issue open just incase we end up supporting OpenSearch outside of just AWS.
I will close this issue since this is more a feature request rather than an issue with our existing setup.
Describe the issue:
Our documentation https://docs.camunda.io/docs/next/self-managed/setup/guides/using-existing-elasticsearch/#connecting-to-existing-elasticsearch-with-a-self-signed-certificate
provides some commands that allows you to create a JKS trust store from a CA certificate file using the following commands:
The relevant option here is
-storepass changeit
, which password-protects the trust store, meaning to get any of the data inside the JKS trust store, you have to supply this password. However, the camunda helm chart does not have any way to supply the password to the JKS file.Furthermore, the
keytool
command line tool does not allow for creating a JKS trust store without password protection.It may be relevant to note that I am using the opensearch operator with mostly default settings, so by default, it deploys opensearch with TLS terminated in the application-level.
Actual behavior: Operate and tasklist fail with the following error:
Expected behavior:
How to reproduce:
Logs:
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.