Optimize Issuer Must not be empty

So we started playing around with a self-managed Camunda 8 installation and we got everything running fine except optimize.

We used a helm install with a nxingx ingress and k3s.

This is the config we run helm with:

global:
  ingress:
    enabled: true
    className: nginx
  identity:
    auth:
      # Disable the Identity authentication for local development
      # it will fall back to basic-auth: demo/demo as default user
      enabled: false

# Disable identity as part of the Camunda core
identity:
  enabled: false

# Disable keycloak
identityKeycloak:
  enabled: false

optimize:
  enabled: true
  contextPath: "/optimize"

# Reduce for Zeebe and Gateway the configured replicas and with that the required resources
# to get it running locally
zeebe:
  clusterSize: 1
  partitionCount: 1
  replicationFactor: 1
  pvcSize: 10Gi

zeebeGateway:
  replicas: 1
  contextPath: "/zeebe"
  ingress:
    grpc:
      enabled: true
      className: nginx

connectors:
  enabled: true
  inbound:
    mode: disabled

elasticsearch:
  master:
    replicaCount: 1
    # Request smaller persistent volumes.
    persistence:
      size: 15Gi

operate:
  contextPath: "/operate"

tasklist:
  contextPath: "/tasklist"

If i access serverip/operate or serverip/tasklist all works fine, but serverip/optimize gives me a 500 and the logs of the optimize pod tell me:

Caused by: java.lang.IllegalArgumentException: issuer must not be empty

is optimize somehow blocked behind enabling auth and or keycloak? Or what am i missing here?

Hi @Morphyum - good question! What version of Camunda are you installing?

Camunda 8.6, I am currently in talks over at Jira and apparently optimize does need the identity component to run unlike tasklist and operate which can run without it.

Hello @Morphyum ,

in fact, Optimize relies on identity authentication, you cannot use Optimize without it.

However, I do not see this being documented. I will pass this on.

Best,

Jonathan

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.