# OpenIDC/mod_auth_openidc

OpenID Certified™ OpenID Connect and FAPI 2 Relying Party module for Apache HTTPd

Repository: https://github.com/OpenIDC/mod_auth_openidc
Canonical: https://ross.abutalabs.com/products/mod_auth_openidc
Homepage: https://www.openidc.com
Language: C
License: Apache-2.0
License Family: permissive
Topics: apache-httpd, openid-connect, openidconnect-client, openidc, c, authentication, oidc, sso, access-control
Last push: 2026-08-30T09:52:32+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 97, longevity 100
- inputs: {"age_days": 4542, "days_push": 3, "days_rel": 23, "gap_med": 29, "n_releases_24m": 22}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1093, forks 332 (observed 2026-09-01T02:13:55.975460+00:00)

## What it is
An OpenID Certified™ Apache HTTPd module implementing OpenID Connect 1.x and FAPI 2.x Relying Party functionality. It lets an Apache web server relay user authentication to an OpenID Connect Provider, establish sessions, and pass identity claims to protected applications or reverse-proxied backends.

## Use cases
- add OpenID Connect SSO login to apps behind Apache
- protect legacy applications with OIDC via reverse proxy without code changes
- enforce claim-based authorization rules with Apache Require directives
- pass id_token and userinfo claims to backend apps via headers
- migrate legacy authentication systems to standards-based OIDC
- secure SPAs and APIs fronted by Apache with single sign-on

## When to choose
- you run Apache HTTPd and need OIDC/OAuth2 authentication in front of applications
- you want OpenID Certified FAPI 2 compliance for high-security scenarios like banking
- you need to add SSO to existing services without modifying them
- you want fine-grained authorization based on OIDC claims

## When to avoid
- your stack uses nginx, Caddy, or another non-Apache web server
- you need a full identity provider rather than a relying party
- you prefer application-level OIDC libraries instead of web-server modules

## Facets
- artifact type: plugin
- maturity: stable
- function: auth, authorization, middleware
- domain: security, web-development, backend, apis
- platform: windows, cpp
- tags: apache-httpd, openid-connect, oidc, sso, relying-party, fapi, c, reverse-proxy, authentication-module, linux, macos, web-server

## Member repositories
- OpenIDC/mod_auth_openidc (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-09-01T02:13:55.975460+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:47:39.984497+00:00, confidence not recorded.
  - readme: https://github.com/OpenIDC/mod_auth_openidc (fetched 2026-09-01T02:13:55.975460+00:00, sha 31098e9db9c0)
  - homepage: https://www.openidc.com (fetched 2026-08-29T12:50:36.187951+00:00, sha 6e59bda9190f)
- Data as of 2026-08-30T08:39:29.467469+00:00.