Getting Started
First touch with Dex
Documentation
Dex documentation — federated OpenID Connect identity service
Dex is an identity service that uses OpenID Connect to drive authentication for other apps. It acts as a portal to other identity providers through “connectors” — letting you defer authentication to LDAP, SAML, or established providers like GitHub, Google, and Active Directory.
// 01 · install
Getting Started
Install Dex, run it locally, and authenticate your first client in minutes.
// 02 · configureConfiguration
Storage, OAuth2 clients, tokens, custom scopes and claims — everything you can configure.
// 03 · connectConnectors
Wire Dex up to GitHub, Google, LDAP, SAML, OIDC, Microsoft and many more identity providers.
// 04 · guidesGuides
Practical walkthroughs: Kubernetes SSO, kubelogin with Active Directory, token exchange, and more.
Architecture
Getting help
- For feature requests and bugs, file an issue.
- For general discussion about using and developing Dex, join the #dex channel on the CNCF Slack or the GitHub Discussions board.
Reporting a security vulnerability
Due to their public nature, GitHub and mailing lists are NOT appropriate places for reporting vulnerabilities. Please refer to the project’s security disclosure process when reporting issues that may be security related.
An Overview of OpenID Connect
Intro to OpenID Connect (basics)
Configuration
Configuring general settings for Dex
Connectors
Documentation about configuration of Dex connectors
Guides
Most common scenarios and how to solve them
Development
Dev Environment Setup, Testing, and Contributing to Dex
Archive
The following documents are no longer maintained and are archived for reference purposes only
