| cmd | ||
| connector | ||
| Documentation | ||
| examples | ||
| scripts | ||
| server | ||
| storage | ||
| vendor | ||
| version | ||
| web/templates | ||
| .gitignore | ||
| .travis.yml | ||
| Dockerfile | ||
| glide.lock | ||
| glide.yaml | ||
| glide_test.go | ||
| Makefile | ||
| README.md | ||
dex - A federated OpenID Connect provider
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:
NOTE: The UIs are extremely bare bones at the moment.
- Navigate to http://localhost:5555/ in your browser.
- Hit "login" on the example app to be redirected to dex.
- Choose the "mock" option to login as a predefined user.
- Approve the example app's request.
- See the resulting token the example app claims from dex.