Support specifying the values for OIDC authentication via a secret key reference

[nogweii]

Proposed functionality

Right now, in order to authenticate with an OIDC provider you must specify the OpenID Connect client ID & secret via a specifically structured Secret and reference the secret in values.yaml. I'd like to propose specific support for those two values in the chart to more flexibly fetch from an arbitrary Secret. Something like the following sample values.yaml:

remoteAuth:
  enabled: true
  backends:
    - social_core.backends.open_id_connect.OpenIdConnectAuth
  oidc:
    existingSecretName: 'netbox-oidc'
    existingSecretClientIdKey: client-id
    existingSecretClientSecretKey: oidc_secret

Further customization, notably groups or roles, would remain the same. It's specifically the two configuration settings for social auth that I think should have special support, SOCIAL_AUTH_OIDC_KEY and SOCIAL_AUTH_OIDC_SECRET.

Use case

Figuring out the exact structure I needed to put my Secret was a surprising pain. I'd like to make it easier for others configuring Netbox with a generic OpenID Connect provider.

OIDC is common enough and well-supported that I think it's worth the special handling. I would not expect to add special support for other social auth backends.

[LeoColomb]

Thanks for filing this issue, @nogweii.
Special thanks for it being well described and redacted.

To keep the chart as simple as possible and to keep the number of values limited, the choice has been made to avoid any specific preset for this setting.
OIDC is as common as Azure AD or OAuth (for the good or for the bad). As soon as one is implemented, others must as well. This is not sustainable for us.
For this reason, I'm going to close this issue.