Identiy: 'Bad request - Requested resource does not exist.' after successful login

[esukram]

What happened:
While logging into Dashboard, a failure is being returned, leading to unsuccessful login:

time="2020-09-17T12:39:46Z" level=info msg="login successful: connector \"local\", username=\"redacted\", preferred_username=\"\", email=\"redacted\", groups=[]"
time="2020-09-17T12:39:46Z" level=error msg="Invalid 'state' parameter provided: not found"

What you expected to happen:
Successful log into the Dashboard.

How to reproduce it (as minimally and precisely as possible):
Using default acre.yaml with static local user and identity inCluster storage.

apiVersion: v1
data:
  config.yaml: |
    issuer: https://gardener.ing.garden.test.local/oidc
    storage:
      type: kubernetes
      config:
        inCluster: true
    web:
      http: "0.0.0.0:5556"
      allowedOrigins:
        - https://gardener.ing.garden.test.local
    oauth2:
      skipApprovalScreen: true
      responseTypes:
      - token
      - code
      - id_token
    staticClients:
    - id: dashboard
      redirectURIs:
        - "https://gardener.ing.garden.test.local/auth/callback"
        - "https://gardener.ing.garden.test.local/oidc/callback"
      name: Gardener Dashboard
      secret: <redacted>
    - id: kube-kubectl
      public: true
      trustedPeers:
      - dashboard
      name: Kubectl
      secret: <redacted>
    enablePasswordDB: true
    staticPasswords:
      - email: admin@<redacted>
        hash: <redacted>
        username: admin

    connectors: []

Anything else we need to know?:
Seems to be related to Dex storage. I found a similar case: dexidp/dex#944
(Precisely this comment)

Environment:

• Version of garden-setup
  • c0e1274
  • cdc23be (after suggestion from @Diaphteiros )
• Where does the underlying base cluster come from and which operating system does it use?
  • AWS EKS 1.17 (eksctl)
• Which cloud provider is configured for the setup?
  • AWS