Repository navigation
Releases: sashyo/minidauth
Releases · sashyo/minidauth
Release list
v0.1.0
First release. minidauth gives the login you already run a key that nobody holds: it lives across the Tide network, and signing, encryption and role changes all need a quorum to agree.
Run it
curl -O https://raw.githubusercontent.com/sashyo/minidauth/main/docker-compose.yml
MC_ADMIN_TOKEN=$(openssl rand -hex 32) docker compose --profile public upNo Java, no Maven, nothing to build. Then bring up a vendor key and try the notes demo.
What works, on the public network
- Sign-in through the Tide enclave, with tokens carrying roles the network has attested
- Role grants that the network refuses until an admin approves them in their enclave
- Encrypting under a policy and decrypting only for a governed role
- Signing under a contract: a payment under the limit gets signed, one over it gets refused by 14 nodes independently
- Examples for Supabase and Clerk, recorded end to end, plus Better Auth. Auth0 and Cognito share the same code but haven't been run against real accounts yet
Worth knowing
- Policy deployment is still gated by this service, not the network. Why.
- The order you bring things up in matters, and getting it wrong strands the key. Follow the quick start in order.
- The image is
linux/amd64only. On Apple Silicon, Docker runs it under emulation.
Images
ghcr.io/sashyo/minidauth:v0.1.0ghcr.io/sashyo/minidauth-tunnel:v0.1.0
The service image includes Tide's compiled MidgardJava jar, shipped with their permission. None of Midgard's source is in the image or this repo.