← Back to home
Comparison · Infra & APIs

mod_auth_openidc vs Skipper

A side-by-side editorial comparison of mod_auth_openidc and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

mod_auth_openidc vs Skipper: at a glance

Featuremod_auth_openidcSkipper
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesoidc, apache, security-audit, session-encryptionreverse-proxy, http-routing, dependency-hygiene, release-per-commit
Last editorial update2h ago12h ago
WebsiteVisit →Visit →

What is mod_auth_openidc?

mod_auth_openidc audited itself, found eight holes, and broke every session on the way out

The Apache OIDC module is in the middle of the most consequential ten days in this window: 2.4.20 on August 1 rebuilt session and cookie encryption around PBKDF2-HMAC-SHA256 key stretching and invalidated every existing session, 2.4.20.1 on August 9 disclosed eight security issues found in an internal audit, and 2.4.20.2 the next morning walked back part of the fallout. The audit findings are not peripheral — the most serious lets a client inject headers that a protected backend trusts as authenticated identity claims on paths the module answers without authenticating. The 2.4.19.x line before it had already shipped an out-of-bounds read and write in the state-cookie parser.

Read the full mod_auth_openidc trajectory →

What is Skipper?

Skipper tags a release per commit — nine in eight days, and none of them change routing.

Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.

Read the full Skipper trajectory →

mod_auth_openidc vs Skipper: editorial side-by-side

M
mod_auth_openidc
INFRA · APIS
6.3

mod_auth_openidc audited itself, found eight holes, and broke every session on the way out

◆ Current state

The Apache OIDC module is in the middle of the most consequential ten days in this window: 2.4.20 on August 1 rebuilt session and cookie encryption around PBKDF2-HMAC-SHA256 key stretching and invalidated every existing session, 2.4.20.1 on August 9 disclosed eight security issues found in an internal audit, and 2.4.20.2 the next morning walked back part of the fallout. The audit findings are not peripheral — the most serious lets a client inject headers that a protected backend trusts as authenticated identity claims on paths the module answers without authenticating. The 2.4.19.x line before it had already shipped an out-of-bounds read and write in the state-cookie parser.

◆ Where it's heading

The project has shifted from feature work to hardening its own attack surface, and it is doing so on its own initiative rather than in response to external reports. That posture has a cost operators are absorbing directly: two backwards-incompatible session format changes in six months, both of which log every user out on upgrade. The 2.4.20.2 release also shows the hardening overshooting and being corrected — unconditional secret masking made debugging impossible, so an opt-in escape hatch was added with a startup warning attached, and a derived-object cache tier added only weeks earlier was removed outright.

◆ Prediction

Expect the 2.4.20.x line to keep absorbing follow-up fixes from the same audit, and any further hardening to arrive with an explicit opt-out after the masking reversal showed operators cannot troubleshoot a protocol exchange they cannot read.

S
Skipper
INFRA · APIS
5.0

Skipper tags a release per commit — nine in eight days, and none of them change routing.

◆ Current state

Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.

◆ Where it's heading

Nothing in these entries points to a direction change; the 0.27 line is in steady maintenance with supply-chain hygiene as the visible priority — oras-go pinned to a released version so osv-scanner stops flagging it, the CodeQL action upgraded, an OPA test hardened to deny requests with truncated bodies. The documentation change is the most revealing item: jwtValidation's behavior was unclear enough to prompt a proposed advisory, and the response was to clarify the docs rather than alter the code.

◆ Prediction

The tag stream will most likely continue at several releases a week with the same composition of dependency bumps and test fixes. These entries show no feature work in flight, so the next notable change is more likely another security-adjacent clarification than a new routing capability.

Alternatives to mod_auth_openidc and Skipper

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either mod_auth_openidc or Skipper.

See all mod_auth_openidc alternatives → · See all Skipper alternatives →

Recent activity from mod_auth_openidc and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 17h agoSkipperPin oras-go to a released version to satisfy osv-scanner
  2. 1d agoSkipperClarify jwtValidation behavior after a proposed advisory
  3. 1d agoSkipperRefactor Valkey Del and ratelimit ring client injection
  4. 1d agoSkipperBump the CodeQL upload-sarif action to 4.37.6
  5. 1d agoSkipperBump 14 Go modules, including OpenTelemetry and go-redis
  6. 1d agomod_auth_openidcOIDCDebugMaskSecrets reopens debug logs, cache tier removed
  7. 1d agomod_auth_openidcInternal audit turns up eight security issues, including an identity-header bypass
  8. 4d agoSkipperFix the proxy listener binding on an insecure address
  9. 10d agomod_auth_openidcPBKDF2 key stretching invalidates all existing sessions
  10. 1mo agomod_auth_openidcOut-of-bounds read and write fixed in the state-cookie parser
  11. 2mo agomod_auth_openidcFixes core dumps under threaded MPM startup load
  12. 5mo agomod_auth_openidcFixes claims-based authorization regression in OAuth RS mode

Frequently asked questions

What is the difference between mod_auth_openidc and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. mod_auth_openidc is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is mod_auth_openidc better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mod_auth_openidc is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to mod_auth_openidc?

Top mod_auth_openidc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mod_auth_openidc alternatives" section above for the current picks, or visit /alternatives/mod-auth-openidc for the full list with editorial commentary on each.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.