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.
 
 
 
 
 
 
Eric Chiang 7084a801d7 *: port oob template 10 years ago
Documentation Documentation/proposals: added a caveats section to upstream refreshing proposal 10 years ago
api api: regenerate protobuf 10 years ago
cmd *: add more comments to the example config 10 years ago
connector *: add a mock connector which takes a username and password for testing 10 years ago
examples Merge pull request #612 from ericchiang/dev-make-example-config-more-readable 10 years ago
scripts *: properly compile version into docker images 10 years ago
server *: port oob template 10 years ago
storage storage/sql: fix typo in keys query 10 years ago
vendor *: revendor 10 years ago
version *: determine version from git 10 years ago
web/templates *: port oob template 10 years ago
.gitignore *: prepare build scripts for a release 10 years ago
.travis.yml *: prepare build scripts for a release 10 years ago
DCO *: add DCO and LICENSE 10 years ago
Dockerfile *: prepare build scripts for a release 10 years ago
LICENSE *: add DCO and LICENSE 10 years ago
Makefile *: build aci at the correct path including version, OS, and arch 10 years ago
README.md *: add more comments to the example config 10 years ago
TODO.md *: add the ability to define passwords statically 10 years ago
glide.lock *: revendor 10 years ago
glide.yaml glide.yaml: add gRPC dependencies 10 years ago
glide_test.go initial commit 10 years ago

README.md

dex - A federated OpenID Connect provider

Caution image

This is an experimental version of dex that is likely to change in incompatible ways.

dex is an OAuth2 server that presents clients with a low overhead framework for identifying users while leveraging existing identity services such as Google Accounts, FreeIPA, GitHub, etc, for actual authentication. dex sits between your applications and an identity service, providing a backend agnostic flavor of OAuth2 called OpenID Connect, a spec will allows dex to support:

  • Short-lived, signed tokens with predefined 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.

Any system which can query dex can cryptographically verify a users identity based on these tokens, allowing authentication events to be passed between backend services.

One such application that consumes OpenID Connect tokens is the Kubernetes API server, allowing dex to provide identity for any Kubernetes clusters.

Getting started

dex requires a Go installation and a GOPATH configured. Clone it down the correct place, and simply type make to compile dex.

git clone https://github.com/coreos/dex.git $GOPATH/src/github.com/coreos/dex
cd $GOPATH/src/github.com/coreos/dex
git checkout dev
make

dex is a single, scalable binary that pulls all configuration from a config file (no command line flags at the moment). Use one of the config files defined in the examples folder to start up dex with an in-memory data store.

./bin/dex serve examples/config-dev.yaml

dex allows OAuth2 clients to be defined statically through the config file. In another window, run the example-app (an OAuth2 client). By default this is configured to use the client ID and secret defined in the config file.

./bin/example-app

Then to interact with dex, like any other OAuth2 provider, you must first visit a client app, then be prompted to login through dex. This can be achieved using the following steps:

  1. Navigate to http://localhost:5555/ in your browser.
  2. Hit "login" on the example app to be redirected to dex.
  3. Choose the "Login with Email" and enter "admin@example.com" and "password"
  4. Approve the example app's request.
  5. See the resulting token the example app claims from dex.