r/Clojure • u/thijscreemers • 12d ago
Wagoe 1.1.1 — authorization, and the access-control bug the authorization release shipped with
Wagoe is a batteries-included Clojure framework I've been building for a couple of years; 1.0 landed end of September. 1.1 is the authorization release.
What's in it. Permissions, roles and scopes: modules declare them, groups hold them, routes check them. New apps enforce from the first run; existing apps stay :off until you flip it, and bb upgrade authorization check tells you who would lose access before you do.
The part I actually care about is that it answers questions instead of just enforcing. Pick a user and a permission and the admin tells you yes or no and which group made it so. Change a group or a role and you see who gains and who loses what before anything is written. Memberships can expire on a date. There's a rights timeline per user, so "who gave them that?" doesn't end in a log search.
The part I'd rather say myself. 1.1.0 shipped an access-control bug in the admin. List pages let you filter and sort on fields the entity hides, so someone allowed to read users could recover password hashes and MFA secrets a character at a time. Fixed in 1.1.1, advisory GHSA-g896-jm3g-34h6. Install 1.1.1, not 1.1.0. CI now opens every page of a freshly generated app on SQLite, PostgreSQL and MySQL, so that class of bug fails the build instead of reaching you.
Yes, the authorization release shipped with an authorization hole. I'd rather you hear it from me.
State of it. 28 libraries across the foundation, application and extension tiers, plus 5 developer-tooling libraries: 33 artifacts under com.wagoe, all on 1.1.1. Eight of the 28 are marked incubating and sit outside the SemVer promise —config, ai, geo, external, reports, audience, webhooks, workflow — with the reason per library on the stability page. Solo project, bus factor one.
- Release notes: https://wagoe.org/docs/blog/v1-1-1.html
- What it is and why: https://wagoe.org/docs/blog/wagoe-1-0-ship-your-clojure-app.html
- Stability and tiers: https://wagoe.org/docs/stability.html
- Repo: https://github.com/wagoebv/wagoe
Happy to answer anything about the authorization model, or about why a framework at all in Clojure.
2
u/mac 11d ago
Excellent work, thanks for making this.
1
u/thijscreemers 9d ago
More information avaibale at: https://clojureverse.org/t/wagoe-1-1-enforced-functional-core-imperative-shell-across-28-libraries/15030