No description
Find a file
m.nabokikh e13aac4963 Switch to gomplate
Signed-off-by: m.nabokikh <maksim.nabokikh@flant.com>
2021-01-29 13:48:05 +04:00
.github chore(deps): update dependabot config 2021-01-15 00:22:52 +01:00
api spelling: register 2020-12-19 22:53:29 -05:00
cmd/dex refactor: version command 2021-01-14 15:55:07 +01:00
connector Update oidc library 2021-01-13 19:56:09 +01:00
docs chore: rename the docs directory 2021-01-14 17:30:04 +01:00
examples Switch to gomplate 2021-01-29 13:48:05 +04:00
pkg connectors: refactor filter code into a helper package 2019-07-03 13:09:40 +02:00
scripts chore: add editorconfig 2020-11-03 20:37:38 +01:00
server Merge pull request #1956 from flant/request-not-supported 2021-01-23 19:43:22 +01:00
storage Merge pull request #1918 from flant/log-device-flow-gc 2021-01-14 18:02:20 +01:00
version *: determine version from git 2016-08-09 14:38:09 -07:00
web chore: add frontend section to dev config (#1913) 2021-01-12 19:20:38 +01:00
.dockerignore chore: cleanup ignore files 2021-01-14 16:27:17 +01:00
.editorconfig chore: add new development configuration 2021-01-28 18:54:38 +01:00
.gitignore chore: improve docker-compose setup 2021-01-14 17:30:02 +01:00
.gitpod.yml Fully automate dev setup with Gitpod (#1868) 2020-11-20 01:00:16 +01:00
.golangci.yml Enable gci and gofumpt 2020-11-03 20:52:14 +01:00
ADOPTERS.md Add flant to ADOPTERS.md 2020-12-15 10:47:24 +04:00
config.dev.yaml chore: add new development configuration 2021-01-28 18:54:38 +01:00
config.yaml.dist chore: add a new basic config example 2021-01-28 18:54:32 +01:00
docker-compose.override.yaml.dist chore: improve docker-compose setup 2021-01-14 17:30:02 +01:00
docker-compose.yaml chore: improve docker-compose setup 2021-01-14 17:30:02 +01:00
Dockerfile Switch to gomplate 2021-01-29 13:48:05 +04:00
entrypoint.sh Switch to gomplate 2021-01-29 13:48:05 +04:00
go.mod chore(deps): bump github.com/stretchr/testify from 1.6.1 to 1.7.0 2021-01-14 22:30:40 +00:00
go.sum chore(deps): bump github.com/stretchr/testify from 1.6.1 to 1.7.0 2021-01-14 22:30:40 +00:00
LICENSE *: add DCO and LICENSE 2016-10-13 11:33:32 -07:00
MAINTAINERS chore: change email address for Nandor 2021-01-14 16:23:46 +01:00
Makefile chore: improve docker-compose setup 2021-01-14 17:30:02 +01:00
README.md docs(readme): fix links 2021-01-15 02:08:23 +01:00

dex - A federated OpenID Connect provider

GitHub Workflow Status Go Report Card go.dev reference Gitpod ready-to-code

logo

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:

eyJhbGciOiJSUzI1NiIsImtpZCI6IjlkNDQ3NDFmNzczYjkzOGNmNjVkZDMyNjY4NWI4NjE4MGMzMjRkOTkifQ.eyJpc3MiOiJodHRwOi8vMTI3LjAuMC4xOjU1NTYvZGV4Iiwic3ViIjoiQ2djeU16UXlOelE1RWdabmFYUm9kV0kiLCJhdWQiOiJleGFtcGxlLWFwcCIsImV4cCI6MTQ5Mjg4MjA0MiwiaWF0IjoxNDkyNzk1NjQyLCJhdF9oYXNoIjoiYmk5NmdPWFpTaHZsV1l0YWw5RXFpdyIsImVtYWlsIjoiZXJpYy5jaGlhbmdAY29yZW9zLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJncm91cHMiOlsiYWRtaW5zIiwiZGV2ZWxvcGVycyJdLCJuYW1lIjoiRXJpYyBDaGlhbmcifQ.OhROPq_0eP-zsQRjg87KZ4wGkjiQGnTi5QuG877AdJDb3R2ZCOk2Vkf5SdP8cPyb3VMqL32G4hLDayniiv8f1_ZXAde0sKrayfQ10XAXFgZl_P1yilkLdknxn6nbhDRVllpWcB12ki9vmAxklAr0B1C4kr5nI3-BZLrFcUR5sQbxwJj4oW1OuG6jJCNGHXGNTBTNEaM28eD-9nhfBeuBTzzO7BKwPsojjj4C9ogU4JQhGvm_l4yfVi0boSx8c0FX3JsiB0yLa1ZdJVWVl9m90XmbWRSD85pNDQHcWZP9hR6CMgbvGkZsgjG32qeRwUL_eNkNowSBNWLrGNPoON1gMg

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

{
  "iss": "http://127.0.0.1:5556/dex",
  "sub": "CgcyMzQyNzQ5EgZnaXRodWI",
  "aud": "example-app",
  "exp": 1492882042,
  "iat": 1492795642,
  "at_hash": "bi96gOXZShvlWYtal9Eqiw",
  "email": "jane.doe@coreos.com",
  "email_verified": true,
  "groups": [
    "admins",
    "developers"
  ],
  "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.

Connectors

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.
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.

Documentation

Reporting a security vulnerability

Due to their public nature, GitHub and mailing lists are NOT appropriate places for reporting vulnerabilities.

Please email the maintainers list to report 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: