ES_SECURITY_USERNAME=abc
ES_SECURITY_PASSWORD=xyz
I hope this helps
Jonathan
Hello Jonathan,
Thanks for the reply, I have tried the same env. variables however still I got the authentication error. Please see below.
09:54:55.995 [main] INFO o.c.o.s.e.OptimizeElasticsearchClientFactory - Initializing Elasticsearch rest client…http://elasticsearch-master:9200 ]]. Please check the connection!
Hello Jonathan,
Any other way that we can provide the ElasticSearch username and password to Optimize?. In the debug log we can see that since the username and password not provided the Optimize is skipping the connection credential setup.09:54:56.725 [main] DEBUG o.c.o.u.e.ElasticsearchHighLevelRestClientBuilder - Elasticsearch username and password not provided, skipping connection credential setup.
So the variables we provided is not accepting.
Hello @krishnakumar797 ,
could you try to set any other variable to prove configuration works in general?
jonathan
Yes @jonathan.lukas , the following env. variable is working which provides the ES host name as below
Please see this file
github.com
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "optimize.fullname" . }}
labels: {{- include "optimize.labels" . | nindent 4 }}
annotations: {{- toYaml .Values.global.annotations | nindent 4 }}
spec:
replicas: 1
selector:
matchLabels:
{{- include "optimize.matchLabels" . | nindent 6 }}
template:
metadata:
labels:
{{- include "optimize.labels" . | nindent 8 }}
{{- if .Values.podLabels }}
{{- toYaml .Values.podLabels | nindent 8 }}
{{- end }}
{{- if .Values.podAnnotations }}
annotations:
Hello @krishnakumar797 ,
I was wrong… the way you can provide user data to Optimize only via environment-config.yaml which has to be mounted.
Here is the docs about it:
Hi @krishnakumar797 ,
Additionally to what Jonathan has already pointed out please also note that there are the following environment variable you can use (these are just so far undocumented):
CAMUNDA_OPTIMIZE_ELASTICSEARCH_SECURITY_USERNAME andCAMUNDA_OPTIMIZE_ELASTICSEARCH_SECURITY_PASSWORD
Thanks @Helene ,
This ENV variables worked and the Optimize was able to connect with ES and created indexes. However now it showing connection refused error to the ZeebeEngine.
12:15:27.198 [PlatformUserIdentityCache-1] ERROR o.c.o.rest.engine.EngineContext - Failed to validate engine camunda-bpm version with error message: Engine didn't respond. Can not verify this engine's version
org.camunda.optimize.service.exceptions.OptimizeRuntimeException: Engine didn't respond. Can not verify this engine's version
thanks @jonathan.lukas , I was able to connect with the ENV. variables provided in the above answer. But however after connecting to the ES, now the Optimize was not able to connect with Zeebe Engine. There is no auth configured for the Zeebe engine. I m getting the below error from Optmize now.
12:15:27.198 [PlatformUserIdentityCache-1] ERROR o.c.o.rest.engine.EngineContext - Failed to validate engine camunda-bpm version with error message: Engine didn't respond. Can not verify this engine's version
org.camunda.optimize.service.exceptions.OptimizeRuntimeException: Engine didn't respond. Can not verify this engine's version
In between I had also tried to provide the Zeebe engine URL as below"OPTIMIZE_CAMUNDABPM_REST_URL": "http://camunda-zeebe.camunda:26502"
I had also tried the following env. variables
"OPTIMIZE_CAMUNDABPM_REST_URL":"http://camunda-zeebe.camunda:26501/engine-rest"
"OPTIMIZE_CAMUNDABPM_WEBAPPS_URL":"http://camunda-zeebe.camunda:26501/camunda"
Please see the log below
12:41:15.427 [main] INFO o.c.o.s.i.PlatformUserIdentityCache - Initializing platform user identity sync.
Hello @krishnakumar797 ,
when connecting Optimize to Zeebe, you need to specify other env variables than for Camunda 7.
As Optimize loads the zeebe data directly from the Elasticsearch export by Zeebe, it needs to know where to search for the data (the assumption is that Zeebe exports to the same Elasticsearch as Optimize):
