Expand description
Deployment static well-known endpoints (#1137 / #1136 serving half).
The DID-anchored trust bootstrap (#1143) fetches four public, integrity-anchored documents from the deployment’s did:web host:
/.well-known/did.json— the deployment DID document (alsoKnownAs → clusterdid:at9p, exactly one Ed25519 Multikey deployment CA, Iroh/QUIC transport reach);/.well-known/at9p/<cid>.cbor— the cluster at9p genesis capsule (self-certifying: BLAKE3-512 over its canonical bytes IS the DID);/.well-known/deployment/registry-service.jwt— the current CA-signed registry deployment credential (one-hour freshness profile)./.well-known/deployment/deployment-authority.log.json— the current root-anchored authority log. Its head must equal the node’s separately provisioned OS-owned anti-rollback checkpoint.
None of these are secret: every one is verified by the fetcher (GATE
canon → hash → sig for the capsule; mutual alsoKnownAs attestation for
the document; CA signature + numeric-date profile for the credential).
Serving them is therefore plain static-file work — but it must happen
SOMEWHERE, and the OAuth service is the deliberate choice: it already
terminates the did:web document surface (/.well-known/did.json), and it
is the only genuinely dual-stack (HTTP + RPC) service in the mesh, so the
deployment’s did:web host can terminate here directly (e.g. via the
stack’s Caddy reverse proxy).
The operator provisions a deployment well-known directory:
<dir>/did.json
<dir>/at9p/<cid>.cbor
<dir>/deployment/deployment-authority.log.json
<dir>/deployment/registry-service.jwt (refreshed hourly by the CA holder)Files are re-read on EVERY request so the external credential-refresh agent needs no service restart. Missing/unreadable files are 404 — the bootstrap fails closed, never on stale in-memory copies.
Functions§
- router
- Mount the deployment well-known routes. Always registered; each handler 404s when no deployment directory is configured, so an OAuth instance that is not the deployment terminator answers exactly like one where the material is absent — no information about configuration leaks.