You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
Go to file
Maksim Nabokikh 2081f7d057
Merge pull request #2620 from mayurwaghmode/master
10 months ago
.github updated gomplate version and added ppc64le support 10 months ago
api chore(deps): update grpc 12 months ago
cmd feat: enable profiling endpoints 1 year ago
connector add config to explicitly set scopes for microsoft connector (#2582) 10 months ago
docs fix: Move enhancements to the docs folder 1 year ago
examples grpc-client: Do not crash on empty response (#2584) 10 months ago
pkg Deprecation warning log message 2 years ago
scripts refactor: remove unused proto scripts 2 years ago
server add PKCE support to device code flow (#2575) 10 months ago
storage add PKCE support to device code flow (#2575) 10 months ago
web fix: back link on password page needs to be explicit. 2 years ago
.dockerignore chore: cleanup ignore files 2 years ago
.editorconfig chore: add new development configuration 2 years ago
.envrc chore: add direnv 2 years ago
.gitignore chore: update gitignore 12 months ago
.gitpod.yml Fully automate dev setup with Gitpod (#1868) 3 years ago
.golangci.yml feat: upgrade Go to 1.18 1 year ago add sigstore to 1 year ago
Dockerfile updated gomplate version and added ppc64le support 10 months ago
LICENSE *: add DCO and LICENSE 7 years ago
MAINTAINERS Add @nabokihms to maintainers list 2 years ago
Makefile chore: upgrade linter 1 year ago Feature: groups in Gitea 1 year ago chore: add new development configuration 2 years ago
config.docker.yaml Switch to slim version of a gomplate and add a comment to docker config 2 years ago
config.yaml.dist Add expiry.refreshToken settings to config.yaml.dist 11 months ago
docker-compose.override.yaml.dist test(connector/ldap): rewrite tests to use a single server instance 2 years ago
docker-compose.test.yaml test(connector/ldap): rewrite tests to use a single server instance 2 years ago
docker-compose.yaml chore: update etcd version in test environments 2 years ago
flake.lock feat: upgrade Go to 1.18 1 year ago
flake.nix feat: upgrade Go to 1.18 1 year ago
go.mod build(deps): bump (#2623) 10 months ago
go.sum build(deps): bump (#2623) 10 months ago

dex - A federated OpenID Connect provider

GitHub Workflow Status Go Report Card Gitpod ready-to-code


Dex is an identity service that uses OpenID Connect to drive authentication for other apps.

Dex acts as a portal to other identity providers through "connectors." This lets dex defer authentication to LDAP servers, SAML providers, or established identity providers like GitHub, Google, and Active Directory. Clients write their authentication logic once to talk to dex, then dex handles the protocols for a given backend.

ID Tokens

ID Tokens are an OAuth2 extension introduced by OpenID Connect and dex's primary feature. ID Tokens are JSON Web Tokens (JWTs) signed by dex and returned as part of the OAuth2 response that attest to the end user's identity. An example JWT might look like:


ID Tokens contains standard claims assert which client app logged the user in, when the token expires, and the identity of the user.

  "iss": "",
  "sub": "CgcyMzQyNzQ5EgZnaXRodWI",
  "aud": "example-app",
  "exp": 1492882042,
  "iat": 1492795642,
  "at_hash": "bi96gOXZShvlWYtal9Eqiw",
  "email": "",
  "email_verified": true,
  "groups": [
  "name": "Jane Doe"

Because these tokens are signed by dex and contain standard-based claims other services can consume them as service-to-service credentials. Systems that can already consume OpenID Connect ID Tokens issued by dex include:

For details on how to request or validate an ID Token, see "Writing apps that use dex".

Kubernetes and Dex

Dex runs natively on top of any Kubernetes cluster using Custom Resource Definitions and can drive API server authentication through the OpenID Connect plugin. Clients, such as the kubernetes-dashboard and kubectl, can act on behalf of users who can login to the cluster through any identity provider dex supports.

  • More docs for running dex as a Kubernetes authenticator can be found here.
  • You can find more about companies and projects, which uses dex, here.


When a user logs in through dex, the user's identity is usually stored in another user-management system: a LDAP directory, a GitHub org, etc. Dex acts as a shim between a client app and the upstream identity provider. The client only needs to understand OpenID Connect to query dex, while dex implements an array of protocols for querying other user-management systems.

A "connector" is a strategy used by dex for authenticating a user against another identity provider. Dex implements connectors that target specific platforms such as GitHub, LinkedIn, and Microsoft as well as established protocols like LDAP and SAML.

Depending on the connectors limitations in protocols can prevent dex from issuing refresh tokens or returning group membership claims. For example, because SAML doesn't provide a non-interactive way to refresh assertions, if a user logs in through the SAML connector dex won't issue a refresh token to its client. Refresh token support is required for clients that require offline access, such as kubectl.

Dex implements the following connectors:

Name supports refresh tokens supports groups claim supports preferred_username claim status notes
LDAP yes yes yes stable
GitHub yes yes yes stable
SAML 2.0 no yes no stable WARNING: Unmaintained and likely vulnerable to auth bypasses (#1884)
GitLab yes yes yes beta
OpenID Connect yes yes yes beta Includes Salesforce, Azure, etc.
OAuth 2.0 no yes yes alpha
Google yes yes yes alpha
LinkedIn yes no no beta
Microsoft yes yes no beta
AuthProxy no yes no alpha Authentication proxies such as Apache2 mod_auth, etc.
Bitbucket Cloud yes yes no alpha
OpenShift no yes no alpha
Atlassian Crowd yes yes yes * beta preferred_username claim must be configured through config
Gitea yes no yes beta
OpenStack Keystone yes yes no alpha

Stable, beta, and alpha are defined as:

  • Stable: well tested, in active use, and will not change in backward incompatible ways.
  • Beta: tested and unlikely to change in backward incompatible ways.
  • Alpha: may be untested by core maintainers and is subject to change in backward incompatible ways.

All changes or deprecations of connector features will be announced in the release notes.


Reporting a vulnerability

Please see our security policy for details about reporting vulnerabilities.

Getting help

  • For feature requests and bugs, file an issue.
  • For general discussion about both using and developing Dex:


When all coding and testing is done, please run the test suite:

make testall

For the best developer experience, install Nix and direnv.

Alternatively, install Go and Docker manually or using a package manager. Install the rest of the dependencies by running make deps.


The project is licensed under the Apache License, Version 2.0.