Hi Datahub team 🙂 OIDC authentication fails. I tried 1st to apply k8s secret, but it didn’t work Then, I’ve added explicitly the keys-values pair for adding all needed Deployment fails. From the output. it looks like the configuration is messed up(it’s working for part of these values) Pls. assist

datahub-frontend:
    enabled: true
    oidcAuthentication:
      enabled: true
      provider: okta
#      clientId:
#        secretRef: datahub-okta-client-secret
#        secretKey: clientid
#      # only needed if you would like to store the client secret in secret
#      clientSecretRef:
#        secretRef: datahub-okta-client-secret
#        secretKey: clientsecret
      oktaDomain: <http://jfrog.okta.com|jfrog.okta.com>
    extraEnvs:
      - name: AUTH_OIDC_ENABLED
        value: true
      - name: AUTH_OIDC_CLIENT_SECRET
        value: xxxxxxxxxxxx 
      - name: AUTH_OIDC_BASE_URL
        value: xxxxxxxxxxxx
      - name: AUTH_OIDC_DISCOVERY_URI
        value: <https://my_okta_domain/.well-known/openid-configuration>
      - name: AUTH_OIDC_SCOPE
        value: <mailto:xxxxx@jxxxx.com|xxxxx@jxxxx.com>
      - name: AUTH_OIDC_BASE_URL
        value: xxxxxxxxxxxxxxx
      - name: AUTH_OIDC_CLIENT_ID
        value: xxxxxxxxxxxxxxxx

Hey, Is

datahub-okta-client-secret

and existing secret in your namespace?

@bulky-electrician-72362 hi Yes, it is. But as you can see it commented out, for it didn’t worked with k8s secret I want 1st to resolve this issue with explicit values under

extraEnvs

Does that work? if not what are the errors you see in the frontend pod?

It’s not gms pod?

is the yaml file the one above?

@bulky-electrician-72362 hi ☀️ Yup….

Hey,

clientId

doesn't support pulling it from a secret.