I took a stab at this and noticed a few things that might be relevant:
- That commit hasn’t made it into a tagged release yet. The only place I don’t get that panic is if I run the
unstabletag. You may already know this, but if (like me) you stumble on this thread with the same issue, be aware that at time of writing, it’s not released yet (despite being in the docs). - An error is thrown in the logs if you don’t specify the
clientidandclientsecret, even if they’re provided in environment variables. The app still initializes and the server comes up, but the button to use the OIDC provider is gone, which appears to be due to this commit. I tried setting those values to an empty string and overriding them from the environment, but it looks like it didn’t take. I do wonder if perhaps I didn’t specify the env variables quite correctly.
For reference, I’m in a k8s environment using xeruf’s fork of the official helm chart. This is a bit of a security concern for me. I know there is technically a way around it by specifying them with files in the config and mounting the secrets to those files, but I haven’t figured out how to negotiate with the helm chart to get that to work. Any advice here would be greatly appreciated.