[ISSUE] Identity Deployment bug in Helm when using existing Keycloak

[djmeph]

Describe the issue:

Under the following conditions:

• Camunda is deployed with camunda-platform helm chart
• Using an existing Keycloak instance
• Setting global.identity.keycloak.contextPath to an empty string ''

Identity is not able to reach Keycloak.

Actual behavior:

Setting global.identity.keycloak.contextPath in the helm chart values to an empty string causes the KEYCLOAK_URL environment variable in the Identity deployment to render with the default context path of /auth/

Expected behavior:

It should render / as the context path.

How to reproduce:

global:
  identity:
    keycloak:
      url:
        protocol: http
        host: keycloak-svc.keycloak-ns.svc.cluster.local
        port: 80
      contextPath: ''
      auth:
        adminUser: admin
        existingSecret: keycloak-admin
        existingSecretKey: admin-password
identityKeycloak:
  enabled: false

Logs:

ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #1. Unable to connect to Keycloak.
 WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #2. Unable to connect to Keycloak.
 WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #3. Unable to connect to Keycloak.
 WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...
ERROR 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Failure #4. Unable to connect to Keycloak.
 WARN 1 --- [           main] i.c.i.i.k.c.KeycloakConfiguration        : Retrying...

Environment:

Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

• Platform: AWS
• Helm CLI version: v3.18.3
• Chart version: 12.5.0
• Values file: (see reproduction steps above)