dexidp/dex
OpenID Connect (OIDC) identity and OAuth 2.0 provider with pluggable connectors
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
2 releases in the last 90 days, the latest 15 days ago, with 276 contributors on GitHub.
Use Cases & Benefits
- Provides an OpenID Connect identity and OAuth 2.0 provider with pluggable connectors for federated authentication.
- Enables seamless integration with multiple identity providers through connectors, simplifying authentication for client applications.
- Use for authenticating users in Kubernetes clusters via OpenID Connect for secure API server access.
- Use for centralizing authentication across diverse identity backends like LDAP, GitHub, and SAML in enterprise environments.
- Use for issuing signed ID Tokens as service-to-service credentials in cloud-native applications requiring standardized identity claims.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
Dex is an identity service that uses OpenID Connect to drive authentication for other apps.
Dex acts as a portal to other identity providers through "connectors." This lets dex defer authentication to LDAP servers, SAML providers, or established identity providers like GitHub, Google, and Active Directory. Clients write their authentication logic once to talk to dex, then dex handles the protocols for a given backend.
ID Tokens are an OAuth2 extension introduced by OpenID Connect and dex's primary feature. ID Tokens are JSON Web Tokens (JWTs) signed by dex and returned as part of the OAuth2 response that attests to the end user's identity. An example JWT might look like:
ID Tokens contains standard claims assert which client app logged the user in, when the token expires, and the identity of the user.
Because these tokens are signed by dex and contain standard-based claims other services can consume them as service-to-service credentials. Systems that can already consume OpenID Connect ID Tokens issued by dex include:
For details on how to request or validate an ID Token, see "Writing apps that use dex".
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+205 stars over 86 days across 8 snapshot days.
Forks
2.0K+49
Open issues
548+28
Compared with peers in Kubernetes
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 8, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| superplanehq/superplane | 9.8K | +1.0K | 75 | 13 days ago |
| kubernetes/kubernetes | 129.0K | +344 | 75 | 4 days ago |
| etcd-io/etcd | 52.7K | +287 | 75 | 19 days ago |
| aquasecurity/trivy | 39.2K | +240 | 75 | 5 days ago |
| agentgateway/agentgateway | 6.1K | +187 | 75 | 14 days ago |
| dexidp/dex | 11.2K | — | 64 | 15 days ago |
| Category median | 39.2K | +287 | 75 | — |
Discover Repositories
Search across tracked repositories by name or description