Skip to content
OpenID Connect Identity (OIDC) and OAuth 2.0 Provider with Pluggable Connectors
Go Other
  1. Go 97.8%
  2. Other 2.2%
Branch: master
Clone or download

Latest commit

techknowlogick Add Gitea connector (#1715)
* Add Gitea connector

* Add details to readme

* resolve lint issue
Latest commit 0a9f565 May 26, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/workflows ci: add mysql service Mar 18, 2020
Documentation Add Gitea connector (#1715) May 26, 2020
api regenerate protobuf code Jul 31, 2019
cmd allow no secret for static public clients May 5, 2020
connector Add Gitea connector (#1715) May 26, 2020
examples Merge pull request #1621 from concourse/pr/passowrd-grant-synced Feb 20, 2020
pkg connectors: refactor filter code into a helper package Jul 3, 2019
scripts Disable travis Jan 30, 2020
server Add Gitea connector (#1715) May 26, 2020
storage storage/kubernetes: remove shadowed ResourceVersion from Connector (#… Apr 7, 2020
vendor Vendor dependencies Jan 31, 2020
version *: determine version from git Aug 9, 2016
web Add icon for OIDC provider May 12, 2020
.dockerignore Replace docker-build script with multi-stage build Sep 21, 2017
.gitignore gitignore: add .idea folder Oct 2, 2019
.golangci.yml increase go lint timeout Mar 19, 2020 Pydio Cells adopters list Aug 28, 2019
DCO *: add DCO and LICENSE Oct 13, 2016
Dockerfile update go to 1.13 and alpine to 3.10 Dec 4, 2019
LICENSE *: add DCO and LICENSE Oct 13, 2016
MAINTAINERS add @sagikazarmark to MAINTAINERS Dec 6, 2019
Makefile Rewrite kubernetes storage test Dec 18, 2019
NOTICE update CoC and legalese Jan 4, 2018 Add Gitea connector (#1715) May 26, 2020 update CoC and legalese Jan 4, 2018
go.mod Revert grpc update Jan 30, 2020
go.sum Revert grpc update Jan 30, 2020
vendor.go *: remove glide and add Go module files Dec 3, 2018

dex - A federated OpenID Connect provider

GitHub Workflow Status Go Report Card GoDoc


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 + dex

Dex's main production use is as an auth-N addon in CoreOS's enterprise Kubernetes solution, Tectonic. Dex runs natively on top of any Kubernetes cluster using Third Party Resources and can drive API server authentication through the OpenID Connect plugin. Clients, such as the Tectonic Console and kubectl, can act on behalf 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.


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
GitLab yes yes yes beta
OpenID Connect yes no (#1065) no beta Includes Salesforce, Azure, etc.
Google yes yes yes alpha
LinkedIn yes no no beta
Microsoft yes yes no beta
AuthProxy no no no alpha Authentication proxies such as Apache2 mod_auth, etc.
Bitbucket Cloud yes yes no alpha
OpenShift no yes no stable
Atlassian Crowd yes yes yes *) beta preferred_username claim must be configured through config
Gitea yes no yes 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 security vulnerability

Due to their public nature, GitHub and mailing lists are NOT appropriate places for reporting vulnerabilities. Please refer to CoreOS's security disclosure process when reporting issues that may be security related.

Getting help

  • For feature requests and bugs, file an issue.
  • For general discussion about both using and developing dex, you can join the #dexidp channel on the Kubernetes Slack, or join the dex-dev mailing list.
You can’t perform that action at this time.