In the Authentication resource with type set to OIDC, the oidcProviders reference ConfigMaps and Secrets that are expected to exist in the `openshift-config` namespace.

Yet when setting a client secret in the console OIDCClient that references a Secret that doesn't exist, none of the conditions set under status.oidcClients reflect that.

Looking into the code shows that there is a OIDCClientSecretGet condition that should be set, yet the code verifying it looks for the console oauth client secret under `openshift-console`. 

Always    

1.Set the Authentication resource "cluster" with type OIDC and an OIDC client with componentName: console & componentNamespace: openshift-console.
2.Set clientSecret.name pointing to a secret that doesn't exist
3.Check the Authentication "cluster" status

apiVersion: config.openshift.io/v1
kind: Authentication
metadata:
  name: cluster
spec:
  type: OIDC
  oauthMetadata:
    name: ""
  oidcProviders:
  - claimMappings:
      groups:
        claim: groups
        prefix: ""
      username:
        claim: email
        prefixPolicy: ""
    issuer:
      audiences:
      - console
      - cli
      issuerCertificateAuthority:
        name: ""
      issuerURL: https://ec2-34-200-245-8.compute-1.amazonaws.com
    name: dex
    oidcClients:
    - clientID: console
      clientSecret:
        name: console-client-secret
      componentName: console
      componentNamespace: openshift-console
    - clientID: oc-cli-test
      clientSecret:
        name: ""
      componentName: cli
      componentNamespace: openshift-console
  serviceAccountIssuer: https://aabdelre-dev.s3.us-east-1.amazonaws.com/aabdelre-devenv-gf55d

No conditions reflecting that the secret doesn't exist

  - componentName: console
    componentNamespace: openshift-console
    conditions:
    - lastTransitionTime: "2025-09-09T13:14:37Z"
      message: secret "console-client-secret" not found
      reason: OIDCClientSecretGet
      status: "True"
      type: Degraded