Open JensBammens opened 6 months ago
Checklist:
argocd version
Describe the bug
Operator release 0.9.1 does not function with Argo CD Dex. Is the OpenShift integration compatible with the static client? When we leave out connectors: [] it results in an invalid Dex config.
connectors: []
To Reproduce
spec: sso: dex: config: | staticClients: - id: argo-workflows-sso name: Argo Workflow secretEnv: ARGO_WORKFLOWS_SSO_CLIENT_SECRET redirectURIs: - https://argoworkflows.example.com/oauth2/callback env: - name: ARGO_WORKFLOWS_SSO_CLIENT_SECRET valueFrom: secretKeyRef: key: client-secret name: argo-workflows-sso openShiftOAuth: true provider: dex additionalConfig: dex.config: | logger: level: debug format: json connectors: [] staticClients: - id: argo-workflows-sso name: Argo Workflow secretEnv: ARGO_WORKFLOWS_SSO_CLIENT_SECRET redirectURIs: - https://argoworkflows.example.com/oauth2/callback
Expected behavior
Authentication should remain functional for OpenShift and there should be a static client available.
Screenshots
Version
v2.10.5+335875d
Logs
Paste any relevant application logs here.
ArgoCD versions 2.10 and below have reached EOL. Can you upgrade and tell us if the issue is still present, please?
Checklist:
argocd version
.Describe the bug
Operator release 0.9.1 does not function with Argo CD Dex. Is the OpenShift integration compatible with the static client? When we leave out
connectors: []
it results in an invalid Dex config.To Reproduce
Expected behavior
Authentication should remain functional for OpenShift and there should be a static client available.
Screenshots
Version
Logs