Dex

Dex is an open source OpenID Connect identity provider that lets applications authenticate users by delegating to existing identity providers such as LDAP,…

  • Security
  • Tools & Utilities
Dex is an open source OpenID Connect identity provider that lets applications authenticate users by delegating to existing identity providers such as LDAP, SAML, Google, GitHub, or Active Directory.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 0 days ago
Popular
8111,269 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
601.5 GB minimum RAM, runs on ARM
Security check
86no serious findings, 2 minor, CI, tests, OpenSSF Scorecard 8.3/10

Availability: platform listings confirmed today, links checked 8 days ago

GitHub stars
11,269
Open issues
534
Last commit
2026-11-20
Latest release
v2.46.1
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (dexidp/dex)

Resources & Compatibility

Minimum requirements: 1.5 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start dex from a settings file Tell dex which settings file to load when you start it, and replace the example identity provider and OAuth2 clients (the apps allowed to ask dex for login) with your real ones before relying on it for real sign-ins. Without correct settings, dex will not know who to trust or where to store login information. source
  • Keep the config and database safe Dex reads its rules from the config file and stores sign-in data in its data store, such as a SQLite (simple file database) file in the example. If these files are lost or not backed up, you can lose your app registrations, user data, or the ability to sign in. source
  • Do a test sign-in first Start the bundled example client app after dex is running and try logging in with your identity provider (the system dex checks for usernames and passwords). This catches missing credentials or wrong settings before real users try to sign in. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How can I confirm my dex configuration works before exposing it to real users?

Run the bundled example client app after dex is running and perform a test sign-in with the identity provider. This catches missing credentials or incorrect settings before real users sign in.

What data should I back up for dex?

Back up the dex config file and its data store, such as the SQLite file used in the example. Losing these can lose app registrations, user data, or the ability to sign in.

Can dex federate multiple upstream identity providers?

Yes, dex sits in front of LDAP, SAML, GitHub, Google, and other identity sources while applications use OpenID Connect. It provides connectors for common providers.

Does dex run on Kubernetes?

Yes, dex runs natively on a Kubernetes cluster using Custom Resource Definitions and can drive API server authentication through the OpenID Connect plugin.

Answers sourced from dexidp.io, dexidp.io, github.com

Community

Collected 53 days ago - public community threads