New idp doesn't show on login page

On a cluster launched with "baselineCapabilitySet: None" set, there is no additional capabilities enabled. After enable console manually by oc patch clusterversion/version, create new idp, the new idp doesn't show up on login page.

4.12.0-0.nightly-2022-11-19-191518

Always

1.Launch a cluster without additional capabilities enabled.
2.Enable console by oc patch:
$  oc patch clusterversion/version --type merge -p '{"spec":{"capabilities":{"additionalEnabledCapabilities":["Console"]}}}'
3.Check the console's accessbility
4.Create a new idp named “qehtpasswd” from console or client. After authentication operator is redeployed, check the idp from login page
$ oc get oauth cluster -o json | jq .spec
{
  "identityProviders": [
    {
      "htpasswd": {
        "fileData": {
          "name": "htpass-secret"
        }
      },
      "mappingMethod": "claim",
      "name": "flexy-htpasswd-provider",
      "type": "HTPasswd"
    },
    {
      "htpasswd": {
        "fileData": {
          "name": "htpasswd-nbqf5"
        }
      },
      "mappingMethod": "claim",
      "name": "qehtpasswd",
      "type": "HTPasswd"
    }
  ]
}

1. The cluster could be launched successfully.
2. Patch works. Console operator and related resources are created.
3. Console could be accessed.
4. The new idp "qehtpasswd" doesn't show up on login page.

4. New idp should show up on login page.