Blog Posts
Published 27 articles
The request lifecycle: why the order of ProxyAuth's gates is part of the contract
A request crosses up to eight gates before it reaches a backend. The order they run in is not an implementation detail — it decides what each mechanism can protect, what can never be blocked by accident, and what an attacker cannot use to get around something else.
/auth, end to end: everything that touches ProxyAuth's own login
One endpoint, two response shapes, and a dozen settings that converge on it. Here is the full path of a login — who may even try, what is verified, what comes back to a browser versus a script, how logout really revokes, and every option that changes a step.
certbot_renew: true — ProxyAuth's built-in ACME client, from first issuance to wildcards
The field is called certbot_renew, but ProxyAuth never runs certbot. It is a native ACME client that binds port 80 by itself, issues one certificate per file with every name as a SAN, renews atomically, reloads without a restart, and handles wildcards through manual DNS-01. Here is all of it, including the parts that still need a human.
Database-backed users: how ProxyAuth keeps memory and the database in sync
ProxyAuth reads every user from memory — no SQL on the request path. Keeping that copy honest against PostgreSQL or MySQL takes two scans with different costs, a trigger for the one change a timestamp query cannot see, and a local LMDB cache that only speaks when the database cannot. Here is the full model, the schema it creates, and the CLI around it.
oidc: on a vhost, completely — the full mechanism, step by step
A vhost with an oidc block turns ProxyAuth into a real OpenID Connect provider for the application behind it. Here is every step — what steps aside, the six endpoints, PKCE, single-use codes, the five checks at /oidc/token, token shapes, signing keys, logout — plus a complete Grafana setup.
Password reset and per-vhost SMTP: from the command to the new password
When one instance fronts several domains, a reset email for one should not come from the other. Here is how smtp and page_change_password resolve per vhost, the two reset flows, the template file and its parser rules, how the port picks the encryption, and what a reset link is actually worth.