From c82a62186a8e0a46fd41e08345a2fa3e54ddffe2 Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:09 +0100 Subject: access: authorization at the API Every request is judged by the registry the node holds: store reads pruned to what the user may read, writes refused where it may not, admin endpoints by protocol capabilities. Without a registry, as before (--protocol-writers for protocol data). Auth plan M1. --- docs/example.toml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'docs/example.toml') diff --git a/docs/example.toml b/docs/example.toml index 26be818..da808ec 100644 --- a/docs/example.toml +++ b/docs/example.toml @@ -80,9 +80,11 @@ htpasswd = "/etc/continuum/htpasswd" # trusted-proxies = ["127.0.0.1", "::1", "unix"] # HTTP API users (from htpasswd or user-header) who may write protocol data under /store/_continuum -# (remake records, members, forget records), e.g. to repair a stuck remake. Such writes -# act on the whole swarm and are logged. Epoch metadata and the swarm ID are never -# writable. +# (remake records, members, forget records), e.g. to repair a stuck remake, in a swarm +# without a user registry. Such writes act on the whole swarm and are logged. Epoch +# metadata and the swarm ID are never writable. With a registry its capabilities decide +# instead (docs/access.md); on a genesis node, those of htpasswd's users named here may +# do everything in the new swarm's registry. # protocol-writers = ["alice"] # With genesis: the new swarm's first users, each may do everything, protocol data and -- cgit v1.3.1