Arsharth/dex
1
0
Fork 0
forked from mystiq/dex
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
470 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 a97cffcd52 connector/saml: refactor tests and add self-signed responses 
Introduces SAML tests which execute full response processing and
compare user attributes. tesdata now includes a full, self-signed
CA and documents signed using xmlsec1.

Adds deprication notices to existing tests, but don't remove them
since they still provide coverage.
2017-04-04 11:11:35 -07:00
api api: Update timestamp type for RefreshTokenRef to int64. 2017-03-17 15:46:39 -07:00
cmd cmd/example-app: fix custom CA behavior 2017-03-24 11:53:28 -07:00
connector connector/saml: refactor tests and add self-signed responses 2017-04-04 11:11:35 -07:00
Documentation Documentation: document dex scopes, claims, and client features 2017-03-28 16:53:06 -07:00
examples examples/grpc-client: clean up the example and add tlsClientCA to ConfigMap. 2017-03-23 16:57:23 -07:00
scripts *: fix spelling using github.com/client9/misspell 2017-03-20 09:16:56 -07:00
server server: use client connected to remove server for gRPC tests 2017-03-28 16:41:39 -07:00
storage storage/static.go: correct the error message that gets displayed. 2017-03-29 11:32:02 -07:00
vendor vendor: revendor 2017-03-24 11:03:30 -07: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-24 11:03:30 -07:00
glide.yaml glide.yaml: update goxmldsig 2017-03-24 11:02:55 -07: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 Documentation: document dex scopes, claims, and client features 2017-03-28 16:53:06 -07: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.