Operate Bugfix 8.2.5

Hi,
i’m looking for more informations about the “bugfix” in 8.2.5 (Release 8.2.5 · camunda/camunda-platform · GitHub)

  • consume CAMUNDA_OPERATE_IDENTITY_REDIRECT_ROOT_URL from env vars (#4351) (#4503)

Login in Operate is not working anymore with 8.2.5 (self managed). I don’t know how this fix affects configuration. Unfortunately, the issue link seems to be dead.

Any hints?

Hi @jbuyer,

How are you configuring Operate - via yml or via env vars?

Could you share your configuration, with any of the sensitive data scrubbed? I can get someone from the Operate team to have a look at it.

Josh

Hi @jwulf ,

i’m using the camunda-platform helm chart in version 8.2.4 for deployment in kubernetes.
I recognized in the meantime that i have a problem configuring a context path for Operate.
Snippet from my configuration values.yaml:

global:
  identity:
    auth:
      enabled: true
      publicIssuerUrl: "https://domain.cloud/auth/realms/camunda-platform"
      operate:
        existingSecret: "existing_secret"
        redirectUrl: "https://domain.cloud/operate"   # redirect with context path
        
camunda-platform:
  operate:
    ....
    contextPath: "/operate"   
    readinessProbe:
      probePath: "/operate/actuator/health/readiness"
    ....

This works well with the images in version 8.2.4 but i got an error with 8.2.5 accessing Operate in the browser when i got redirected to the identity login page (“We are sorry… Invalid parameter: redirect_uri”). I tried different configurations but without success.

I finally changed the configuration giving up the context path and everything works as expected.

global:
  identity:
    auth:
      enabled: true
      publicIssuerUrl: "https://domain.cloud/auth/realms/camunda-platform"
      operate:
        existingSecret: "existing_secret"
        redirectUrl: "https://domain-operate.cloud"   
        
camunda-platform:
  operate:
    ....
#    contextPath: "/operate"   
#    readinessProbe:
#      probePath: "/operate/actuator/health/readiness"
    ....

Maybe i just don’t fully understand how a context path for Operate has to be configured.
Since it is not strictly necessary using a context path i’m just fine with the configuration without it.

Jürgen

@jbuyer, there is a bug in the v8.2.5 apps, and I’m working on a hotfix for it in the Helm chart till it’s fixed in the apps.

Follow for more details:

1 Like