OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors
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.
 
 
 
 
 
 
Amruta Chitnis ea75973547 web: Adds tectonic specific files 9 years ago
Documentation Merge pull request #708 from ericchiang/ldap-security-docs 9 years ago
api api: adding a gRPC call for listing passwords. 9 years ago
cmd cmd/example-app: use a non-empty state 9 years ago
connector *: switch oidc client to github.com/coreos/go-oidc 9 years ago
examples *: add theme based frontend configuration 9 years ago
scripts *: travis tests and build scripts should use Go 1.7.3. 10 years ago
server *: add theme based frontend configuration 9 years ago
storage api: adding a gRPC call for listing passwords. 9 years ago
vendor vendor: revendor 9 years ago
version *: determine version from git 10 years ago
web web: Adds tectonic specific files 9 years ago
.gitignore *: prepare build scripts for a release 10 years ago
.travis.yml *: travis tests and build scripts should use Go 1.7.3. 10 years ago
DCO *: add DCO and LICENSE 10 years ago
Dockerfile *: add theme based frontend configuration 9 years ago
LICENSE *: add DCO and LICENSE 10 years ago
Makefile *: add theme based frontend configuration 9 years ago
README.md *: document the GitHub connector 9 years ago
glide.lock vendor: revendor 9 years ago
glide.yaml *: switch oidc client to github.com/coreos/go-oidc 9 years ago
glide_test.go initial commit 10 years ago

README.md

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.