Arsharth/dex
1
0
Fork 0
forked from mystiq/dex
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
426 commits 27 branches 73 tags 23 MiB
Go 97.8%
CSS 0.6%
HTML 0.6%
Makefile 0.5%
Dockerfile 0.2%
Other 0.2%
Find a file
Eric Chiang ee27a4f9f4 *: only use docker when releasing, update to Go 1.8, remove aci scripts 
This change modifies our release process to only require Docker
when building a release and updates our released binary to use Go
1.8. It also removes our .aci scripts, which we've not been
regularly building.

A nice consequence is that OSX users can now build a release image.
2017-03-09 10:46:09 -08:00
api api: adding a gRPC call for revoking refresh tokens. 2017-02-15 07:48:20 -08:00
cmd *: update go-oidc and use standard library's context package 2017-03-08 10:33:19 -08:00
connector *: update go-oidc and use standard library's context package 2017-03-08 10:33:19 -08:00
Documentation *: only use docker when releasing, update to Go 1.8, remove aci scripts 2017-03-09 10:46:09 -08:00
examples examples/grpc-client: minor corrections in the dex client example. 2017-03-03 15:58:30 -08:00
scripts *: only use docker when releasing, update to Go 1.8, remove aci scripts 2017-03-09 10:46:09 -08:00
server *: update go-oidc and use standard library's context package 2017-03-08 10:33:19 -08:00
storage *: update go-oidc and use standard library's context package 2017-03-08 10:33:19 -08:00
vendor vendor: revendor 2017-03-08 10:33:36 -08:00
version *: determine version from git 2016-08-09 14:38:09 -07:00
web web/static/main.css: fix typo. 2017-02-20 08:48:36 -08:00
.dockerignore *: only use docker when releasing, update to Go 1.8, remove aci scripts 2017-03-09 10:46:09 -08:00
.gitignore *: prepare build scripts for a release 2016-10-05 23:43:44 -07:00
.travis.yml *: only use docker when releasing, update to Go 1.8, remove aci scripts 2017-03-09 10:46:09 -08: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 2017-03-08 10:33:36 -08:00
glide.yaml *: update go-oidc and use standard library's context package 2017-03-08 10:33:19 -08:00
glide_test.go *: add 'make revendor' and tests to catch incorrect glide usage 2016-12-22 11:52:24 -08:00
LICENSE *: add DCO and LICENSE 2016-10-13 11:33:32 -07:00
Makefile *: only use docker when releasing, update to Go 1.8, remove aci scripts 2017-03-09 10:46:09 -08:00
README.md *: wire up SAML POST binding 2017-01-09 18:30:58 -08:00

README.md

dex - A federated OpenID Connect provider

Travis GoDoc Go Report Card

logo

Dex is an OpenID Connect server that connects to other 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:

Kubernetes + dex

Dex's main production use is as an auth-N addon in CoreOS's enterprise Kubernetes solution, Tectonic. Dex runs natively on top of any Kubernetes cluster using Third Party Resources and can drive API server authentication through the OpenID Connect plugin. Clients, such as the Tectonic Console and kubectl, can act on behalf users who can login to the cluster through any identity provider dex supports.

More docs for running dex as a Kubernetes authenticator can be found here.

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.