No description
Find a file
2016-12-01 13:41:56 -08:00
api api: adding a gRPC call for listing passwords. 2016-11-17 16:56:54 -08:00
cmd cmd/example-app: use a non-empty state 2016-12-01 09:05:56 -08:00
connector *: switch oidc client to github.com/coreos/go-oidc 2016-11-22 13:29:17 -08:00
Documentation Merge pull request #708 from ericchiang/ldap-security-docs 2016-11-28 17:07:24 -08:00
examples *: add theme based frontend configuration 2016-11-30 17:20:21 -08:00
scripts *: travis tests and build scripts should use Go 1.7.3. 2016-11-03 12:28:53 -07:00
server *: add theme based frontend configuration 2016-11-30 17:20:21 -08:00
storage api: adding a gRPC call for listing passwords. 2016-11-17 16:56:54 -08:00
vendor vendor: revendor 2016-11-22 13:29:17 -08:00
version *: determine version from git 2016-08-09 14:38:09 -07:00
web web: Updates classes in templates 2016-12-01 13:41:56 -08:00
.gitignore *: prepare build scripts for a release 2016-10-05 23:43:44 -07:00
.travis.yml *: travis tests and build scripts should use Go 1.7.3. 2016-11-03 12:28:53 -07:00
DCO *: add DCO and LICENSE 2016-10-13 11:33:32 -07:00
Dockerfile *: add theme based frontend configuration 2016-11-30 17:20:21 -08:00
glide.lock vendor: revendor 2016-11-22 13:29:17 -08:00
glide.yaml *: switch oidc client to github.com/coreos/go-oidc 2016-11-22 13:29:17 -08:00
glide_test.go initial commit 2016-07-26 15:51:24 -07:00
LICENSE *: add DCO and LICENSE 2016-10-13 11:33:32 -07:00
Makefile *: add theme based frontend configuration 2016-11-30 17:20:21 -08:00
README.md *: document the GitHub connector 2016-11-22 12:53:46 -08:00

dex - A federated OpenID Connect provider

GoDoc

logo

Dex is an OpenID Connect server that allows users to login through upstream identity providers. Clients use a standards-based OAuth2 flow to login users, while the actual authentication is performed by established user management systems such as Google, GitHub, FreeIPA, etc.

OpenID Connect is a flavor of OAuth that builds on top of OAuth2 using the JOSE standards. This allows dex to provide:

  • Short-lived, signed tokens with standard fields (such as email) issued on behalf of users.
  • "well-known" discovery of OAuth2 endpoints.
  • OAuth2 mechanisms such as refresh tokens and revocation for long term access.
  • Automatic signing key rotation.

Standards-based token responses allows applications to interact with any OpenID Connect server instead of writing backend specific "access_token" dances. Systems that can already consume ID Tokens issued by dex include:

Documentation

Getting help

  • For bugs and feature requests (including documentation!), file an issue.
  • For general discussion about both using and developing dex, join the dex-dev mailing list.
  • For more details on dex development plans, check out the GitHub milestones.