[ISSUE] identity client-id for OIDC is not set when an existingSecret is used #2727
Closed
1 task done
Labels
cycle/alpha3
Tasks will be done in alpha3 cycle
kind/issue
Unidentified issue, it could be a bug, misconfig, or anything in between
platform/aws
Issues related to AWS
platform/gcp
Issues related to GCP
version/8.5
Camunda applications/cycle version
version/8.6
Camunda applications/cycle version
version:10.4.7
Issues and PRs related to chart version 10.4.7
version:11.1.1
Issues and PRs related to chart version 11.1.1
Milestone
Describe the issue:
When
global.identity.auth.[component].existingSecret.name
is set in the values.yaml, theclient-id
in the identity configmap is not populated with a value.This is because the if statement only allows string literal values and not existingSecrets:
camunda-platform-helm/charts/camunda-platform-8.5/templates/identity/configmap.yaml
Line 21 in c399f09
The above function only references the string literal:
camunda-platform-helm/charts/camunda-platform-8.5/templates/identity/_helpers.tpl
Line 219 in c399f09
It does not reference
.Values.global.identity.auth.identity.existingSecret.name
as well to provide an existing k8s secret.This is the case for 8.4 and above
Expected behavior:
I expect OIDC to function with existingSecrets and string literal values.
Logs:
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.
Tasks
The text was updated successfully, but these errors were encountered: