Could not login using OpenID Connect

[29x10]

I am configuring auth0 as openid provider, but when I use oc login --token=id_token, it says

error: The token provided is invalid or expired.

Version

[provide output of the openshift version or oc version command]

Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.7-201907171753+1e3cff4-dirty", GitCommit:"1e3cff4", GitTreeState:"dirty", BuildDate:"2019-07-18T00:11:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+4b86cc5", GitCommit:"4b86cc5", GitTreeState:"clean", BuildDate:"2019-07-24T19:42:25Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}

Steps To Reproduce

Here is my identity configuration for openid:

    - mappingMethod: claim
      name: auth0
      openID:
        claims:
          email:
            - email
          'name:':
            - email
          preferredUsername:
            - email
        clientID: my_client_id
        clientSecret:
          name: openid-client-secret-qbmwv
        extraScopes:
          - email
        issuer: 'https://xxx.auth0.com'
      type: OpenID

Current Result

error: The token provided is invalid or expired.

Expected Result

authenticate successfully

Additional Information

[try to run $ oc adm diagnostics (or oadm diagnostics) command if possible]
[if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5]
[consider attaching output of the $ oc get all -o json -n <namespace> command to the issue]
[visit https://docs.openshift.org/latest/welcome/index.html]

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.