Dex: one OIDC front door for many identity sources

Scroll or pinch to zoom, drag to move, double-click to zoom in 100% SVG PNG Back to the post
Dex architecture: a client application sends an authentication request to Dex, which uses a connector to reach upstream identity sources such as LDAP, GitHub or another OIDC provider. Dex keeps state in Kubernetes CRDs, a SQL database or etcd and signs tokens with rotating keys published as JWKS. The Kubernetes API server verifies ID tokens with those keys, a gRPC API manages clients and users, and.