No description
This repository has been archived on 2022-08-17. You can view files and clone it, but cannot push or open issues or pull requests.
Find a file
Eric Chiang 144fa41a23 Merge pull request #569 from ericchiang/dev-response-types-supported-discovery
dev branch: set response types supported in discovery based on server config
2016-08-29 11:56:42 -07:00
cmd *: set response types supported in discovery based on server config 2016-08-25 16:18:09 -07:00
connector rename 2016-08-10 22:31:42 -07:00
Documentation rename 2016-08-10 22:31:42 -07:00
examples rename 2016-08-10 22:31:42 -07:00
scripts *: determine version from git 2016-08-09 14:38:09 -07:00
server *: set response types supported in discovery based on server config 2016-08-25 16:18:09 -07:00
storage rename 2016-08-10 22:31:42 -07:00
vendor *: revendor 2016-08-08 11:49:47 -07:00
version *: determine version from git 2016-08-09 14:38:09 -07:00
.gitignore initial commit 2016-07-26 15:51:24 -07:00
.travis.yml *: enable travis testing 2016-08-18 15:40:13 -07:00
Dockerfile rename 2016-08-10 22:31:42 -07:00
glide.lock *: revendor 2016-08-08 11:49:47 -07:00
glide.yaml rename 2016-08-10 22:31:42 -07:00
glide_test.go initial commit 2016-07-26 15:51:24 -07:00
Makefile *: fix testing with the race detector 2016-08-10 23:00:32 -07:00
README.md *: fix instructions in README for downloading and running dex 2016-08-11 15:20:39 -07:00

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:

NOTE: The UIs are extremely bare bones at the moment.

  1. Navigate to http://localhost:5555/ in your browser.
  2. Hit "login" on the example app to be redirected to dex.
  3. Choose the "mock" option to login as a predefined user.
  4. Approve the example app's request.
  5. See the resulting token the example app claims from dex.