biscuit-based identity and authorization I’m working on https://www.hessra.net/ , an identity + authorization service built around [Biscuits]( https://www.biscuitsec.org/ ) instead of JWTs. The goal is to decompose auth primitives so they’re easier to use in service-to-service cases, while also showing off what Biscuit tokens make possible. JWTs feel like problems waiting to happen. I think biscuits give stronger gua…
Are Eclipse Biscuits related to Google Macaroons? https://research.google/pubs/macaroons-cookies-with-contextu... (what a word salad that is...)
Key differences from macaroons:
- Crypto model: Macaroons use HMAC, so every verifier needs the shared secret. Biscuits use public/private keypairs so any verifier with the public key can check validity.
- Expressiveness: Macaroons only add caveats (restrictions). Biscuits can encode facts, rules, and checks, enabling more complex policies to travel with the token. so you can attest and attenuate (and do some other tricky stuff if you want)
- Delegation: Both support attenuation, but biscuits do it with signed blocks that are verifiable and can be chained across services.
So conceptually similar, but biscuits aim to be more decentralized and policy-rich.