// the take
An Apache httpd module, written in C, that turns Apache into an OpenID Connect Relying Party and OAuth 2.0 resource server, including FAPI 2.0 support. It's for teams standardizing authentication at the Apache/reverse-proxy layer in front of apps that shouldn't need to implement OIDC themselves, especially regulated-industry setups that need FAPI or mTLS-bound tokens.
Spec coverage is unusually deep for an RP library: PKCE, DPoP, mTLS-bound tokens, PAR, FAPI 2.0 message signing, front- and back-channel logout, session management - most OIDC libraries stop well short of this. The test/fuzz corpus is extensive and targets exactly the attack surface that matters for an RP (JWT/JWKS parsing, cookie handling, authz responses, discovery responses), which is the right place to put fuzzing effort in a C module that parses untrusted input. It genuinely holds OpenID Certified status rather than just claiming compliance. Supports shm/file/memcache/redis cache backends so sessions survive restarts and work across a cluster, and it sits in front of existing apps as a reverse proxy without requiring any app-side changes.
It's a native C module loaded into the Apache worker process - a bug in parsing a malicious id_token or JWKS response is a potential crash or memory-safety issue for the whole server, not a contained exception, so the fuzzing investment is doing real load-bearing work rather than being a nice-to-have. The open-source Redis backend doesn't support TLS or Sentinel/Cluster - that's gated behind a commercial license, so a real HA deployment with Redis means either rolling your own TLS termination in front of Redis or paying. It only runs on Apache httpd; there's no path to nginx, Caddy, Envoy or any other proxy, so adopting it means standardizing your whole stack on Apache. Configuration lives in httpd.conf directives rather than a structured file, so there's no schema validation - typos in OIDCProviderMetadataURL or similar surface as runtime auth failures, not config-time errors.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →