-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
External OIDC setup docs is confusing for customers #4619
Comments
@conceptualshark can you please review and PR? |
Left an open question with distribution on how to best handle this, as it seems related to either updating the Connectors docs for a better experience, or may need additional info on how/when env vars do not override Helm values. I think the ultimate impact may need to be in the Connectors config guide vs the OIDC docs. |
This came up again while discussing this support ticket. None of the support engineers were sure how to interpret the Connectors config (as shown in the screenshot).
![]() @alessandrocavalli, please add/update if I missed something or anything is not correct. |
Thanks @akeller for reaching out!
--> Please review this PR (adds a simple or in the statement).
--> @sbuettner do you have the context to answer these and could clarify it in the doc section 🙏 ? |
The Connectors act as a Client for Operate and would need this configuration. |
On this page: https://docs.camunda.io/docs/self-managed/setup/guides/connect-to-an-oidc-provider/
At the configuration section there are environment variables and Helm values offered. However, it is not explicitly specified that they are in a XOR relation - i.e. the customer should not use both at the same time, but either the helm values or the environment variables. This confusion lead to incorrect setups in customer environments, e.g.: https://jira.camunda.com/browse/SUPPORT-24589
Please append an additional note that only one of these options should be used: either helm values or env variables, but not both!
The text was updated successfully, but these errors were encountered: