go-oidc

A Go client library for OpenID Connect, built on top of golang.org/x/oauth2.

Library
Go
vv2.5.0+incompatible
2,502 stars
Apache License 2.0

Repository Health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum. How we score it →
63 /100 Good
Development Activity 56
Maintenance 24
Community 72
Maturity 60
Momentum 40

Technical Analysis

AI-assessed by reading the actual repository — architecture, code quality, innovation, and documentation. How we score it →
79 /100 Good
Architecture 85
Code Quality 88
Innovation 62
Learning Curve 80

go-oidc adds OpenID Connect support to Go applications that already use golang.org/x/oauth2 for OAuth2 flows. It handles provider discovery via the .well-known/openid-configuration document, exposes the discovered authorization and token endpoints as a standard oauth2.Endpoint, and verifies ID Tokens against the provider’s published JSON Web Key Set — checking signature, issuer, audience, and expiry so callers don’t have to hand-roll JWT validation.

Maintained by CoreOS (now under Red Hat/IBM) and imported by well over a thousand open source projects, it is one of the most widely used Go OIDC clients and is commonly used to integrate with identity providers like Google, Microsoft Entra ID, Okta, Auth0, and Kubernetes service-account tokens, as well as workload-identity flows such as GitHub Actions OIDC.

What You Get

  • OpenID Connect discovery via oidc.NewProvider, resolving the issuer’s authorization, token, device-authorization, userinfo, and JWKS endpoints from its .well-known/openid-configuration document
  • Provider.Endpoint() returning a ready-to-use oauth2.Endpoint so the standard golang.org/x/oauth2 package drives the actual authorization-code exchange
  • An IDTokenVerifier that checks JWT signature, issuer, audience, expiry, and (optionally) access-token hash binding against a remote or static key set
  • NewRemoteKeySet for long-lived, self-refreshing JWKS caching, plus a StaticKeySet for tests or key material supplied out of band
  • Provider.UserInfo for querying the OpenID Connect userinfo endpoint with an oauth2 token source
  • A ProviderConfig escape hatch for providers that don’t implement discovery or host it at a non-spec path
  • Logout token verification (VerifyLogout) for OpenID Connect back-channel logout flows
  • An oidctest subpackage exposing test helpers for exercising the verifier without a live identity provider

Common Use Cases

  • Adding “Sign in with Google/Microsoft/Okta” login to a Go web app on top of an existing oauth2.Config
  • Verifying Kubernetes service-account OIDC tokens or GitHub Actions workload-identity tokens for keyless CI/CD authentication
  • Building an internal SSO gateway that federates to multiple enterprise identity providers via standard OIDC discovery
  • Validating ID tokens received from a client-side SPA before establishing a server-side session
  • Implementing OpenID Connect back-channel logout handling in a multi-service backend

Under The Hood

Architecture

go-oidc is organized as a single oidc package with a small, composable surface: Provider (discovery result), IDTokenVerifier (validation), and KeySet (a pluggable interface with NewRemoteKeySet and StaticKeySet implementations in jwks.go). oidc.go owns discovery (NewProvider) and the ID Token/UserInfo data model; verify.go owns the IDTokenVerifier/Config validation logic and delegates signature checking to whatever KeySet it was constructed with; jwks.go implements the two KeySet variants, using github.com/go-jose/go-jose/v4 for JWS parsing; logout.go layers back-channel logout token verification on the same primitives. There is no global state beyond a per-Provider mutex guarding a lazily-created shared remote key set, and HTTP clients are threaded through context.Context via ClientContext/oauth2.HTTPClient, so swapping the transport (e.g. for testing or custom TLS) requires no API changes — a change to the KeySet interface would be the one modification that ripples through every consumer, since both discovery-based and manual verifiers depend on it.

Tech Stack

The module (github.com/coreos/go-oidc/v3, requiring Go 1.25) has exactly two runtime dependencies: golang.org/x/oauth2 for the underlying OAuth2 token exchange and HTTP client context plumbing, and github.com/go-jose/go-jose/v4 for JWS/JWK parsing and signature verification (RS256/384/512, ES256/384/512, PS256/384/512, and EdDSA). There is no web framework, ORM, or database layer — this is a pure protocol/client library meant to be embedded in a caller’s own HTTP handlers, with releases and dependency updates driven by GitHub Actions and Dependabot.

Code Quality

Each core source file has a directly corresponding test file of comparable or greater size (e.g. oidc_test.go at 881 lines against oidc.go at 687, verify_test.go at 622 lines against verify.go at 340, plus a dedicated oidctest package providing reusable test doubles), indicating deliberate, thorough test coverage of discovery, verification, and logout paths rather than incidental testing. Errors are returned as typed values (IssuerMismatchError, TokenExpiredError) or wrapped with fmt.Errorf/%v rather than swallowed, exported identifiers carry Go-doc comments with runnable examples, and CI runs via .github/workflows/test.yaml on every change alongside Dependabot-managed dependency bumps.

What Makes It Unique

Rather than binding to one identity provider’s SDK, go-oidc implements the OpenID Connect discovery and verification spec generically, so the same client code works against any spec-compliant issuer — consumer providers like Google and Apple, enterprise providers like Entra ID and Okta, and workload-identity issuers like GitHub Actions or Kubernetes — while deliberately deferring the OAuth2 authorization-code exchange itself to the standard golang.org/x/oauth2 package instead of reimplementing it, keeping the library’s scope narrow and its behavior predictable.

Used by 27 apps in this directory

Go
52%
Apache 2.0

opencloud

File Storage

6,291

Open source file management and collaboration platform that keeps your data under your control, no database required.

View details
86
Repo Health
80
Technical
68
Dependency
Built with
Go 52%
Gherkin 33%
PHP 11%
Updated 1 weeks ago
Go
91%
Apache 2.0

Ory Kratos

Authentication

13,947

API-first identity and user management that handles login, registration, MFA, and recovery so your application never has to.

View details
54
Repo Health
78
Technical
64
Dependency
Built with
Go 91%
Updated 3 months ago
Go
40%
Apache 2.0

Rill

Analytics · Data Engineering

2,985

The fastest BI tool for humans and agents — define metrics, models, and dashboards as code and query them instantly on ClickHouse or DuckDB.

View details
88
Repo Health
88
Technical
65
Dependency
Built with
Go 40%
TypeScript 38%
Svelte 20%
Updated 1 weeks ago
TypeScript
51%
Other

SigNoz

Analytics · Monitoring

32,543

Self-host your entire observability stack — logs, metrics, traces, and LLM monitoring — in one OpenTelemetry-native platform, without the Datadog bill.

View details
92
Repo Health
83
Technical
64
Dependency
Built with
TypeScript 51%
Go 37%
Updated 1 weeks ago
Go
54%
AGPL 3.0

Uptrace

Devops · Monitoring

4,311

Unified open-source APM that collects OpenTelemetry traces, metrics, and logs into a single self-hosted platform backed by ClickHouse.

View details
70
Repo Health
70
Technical
65
Dependency
Built with
Go 54%
Vue 34%
Updated 4 weeks ago
Go
88%
Apache 2.0

Miniflux

Bookmarks Archiving

9,895

Privacy-first, opinionated feed reader built for speed and control—no bloat, no trackers, no JavaScript overhead.

View details
89
Repo Health
80
Technical
79
Dependency
Built with
Go 88%
Updated 2 weeks ago
Go
69%
AGPL 3.0

Vikunja

Project Management

5,979

Self-hosted task management with natural-language quick-add, multiple views, and a fully documented REST API — your tasks, your infrastructure, zero lock-in.

View details
86
Repo Health
81
Technical
65
Dependency
Built with
Go 69%
TypeScript 20%
Updated 1 weeks ago
Go
79%
MIT

Wakapi

Analytics · Developer Tools

4,471

Self-hosted WakaTime-compatible coding statistics backend that gives developers full control over their coding activity data.

View details
90
Repo Health
77
Technical
72
Dependency
Built with
Go 79%
HTML 11%
Updated 1 weeks ago
Go
97%
BSD 3

Weaviate

Databases · Search

16,940

Open-source vector database combining semantic search, hybrid queries, RAG, and image search in a single cloud-native system built for production scale.

View details
91
Repo Health
85
Technical
68
Dependency
Built with
Go 97%
Updated 1 weeks ago

Join founders buildingwith open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on Substack
Join 750+ subscribers