// the take
An nginx module that lets nginx gate a location block behind Shibboleth's FastCGI authorizer, using nginx's subrequest mechanism rather than Apache's mod_shib. It's for ops teams running nginx in front of apps that need SAML2/SSO via Shibboleth, which in practice mostly means higher-ed and research institutions tied into federations like InCommon or eduGAIN.
Attribute propagation is handled two ways depending on backend: shib_request_set exposes attributes as nginx variables you can push into fastcgi_param/uwsgi_param/scgi_param for any FastCGI-speaking backend, while shib_request_use_headers covers proxy_pass backends that can't read server params. CI actually runs integration tests with Test::Nginx against real nginx builds on every push, not just unit tests on isolated C functions. It composes with nginx's existing auth primitives via satisfy, so you're not forced into an all-or-nothing auth model.
It's a compiled nginx module (static or dynamic), so you're building nginx yourself or relying on nginx's own pkg-oss packaging — no distro packages, which is real ops overhead compared to a drop-in config. The header-based attribute path is a spoofing trap by design: you must manually enumerate every attribute your app reads and clear it with more_clear_input_headers, and the README admits this is easy to get wrong, especially since apps often fall back to headers even when you think you're using env vars. Request/response bodies aren't forwarded to or from the authorizer because of how nginx subrequests work, which is fine for Shibboleth itself but rules out some other FastCGI authorizers the module claims to support. Last commit was November 2024 with a small maintainer pool for C code sitting directly in the auth path — that's the kind of project where a dormant year matters more than it would for a typical library.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →