From de12c862b3f4e69290c8e93b3b4520024ba458f6 Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:09 +0100 Subject: access: the users endpoints /admin/users: list, add (one or several), remove, disable, grant and revoke capabilities; each one change, refused if it would lock its writer out. Capabilities as the store's paths name them. Auth plan M1. --- docs/trust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/trust.md') diff --git a/docs/trust.md b/docs/trust.md index bcf9bc7..fd37638 100644 --- a/docs/trust.md +++ b/docs/trust.md @@ -43,7 +43,7 @@ reverse proxy). It listens on `127.0.0.1:3000` by default (`--bind-addr`) and sp plain HTTP: to expose it, put a TLS proxy in front. What each user may do is the swarm's: its user registry, in the document, gives each capabilities by path, to read and to write, protocol data apart ([`access.md`](access.md)); a user the registry doesn't have -may do nothing. In a swarm without a registry (one from before it), all users may read +may do nothing. In a swarm without a registry (started without one), all users may read and write user data and use the admin endpoints, and only those in `--protocol-writers` write protocol data. Epoch metadata and the swarm ID are never writable. The `/debug` endpoints exist only with `--debug-api`. -- cgit v1.3.1