aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/federation')
-rw-r--r--docs/guides/federation/running-a-node.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md
index e08a47e..ea51f8a 100644
--- a/docs/guides/federation/running-a-node.md
+++ b/docs/guides/federation/running-a-node.md
@@ -71,6 +71,15 @@ alone, so that a party listing many nodes can't be all of a node's neighbours.
what an operator does to the store (`/admin/events/…`): for an application, or
someone watching, that needn't act for the node. A token is taken by the node that
issued it only, and gives what its user may do.
+* **A party's keys** log in to every node holding the store, without a password: a
+ challenge (`POST /auth/challenge`) signed with one of the keys that sign for the party
+ there (those its current version names, or of its key set as it counts), for the
+ namespace `continuum-login`, gives a token as the party (`POST /auth/login/party`).
+ Such a session does federation work alone: what a reader does, and putting events
+ (`POST /events`), while that key signs for the party (`401` once it doesn't). So a
+ party's people, each with a key of its set, work with the federation through any node
+ that holds it, as no operator has to let them in, and with nothing of an operator's
+ powers.
* **The events** (`docs/openapi.yaml`, Events): `GET /events` (the store's ID, its
checkpoint, its heads, how many events it took, the node's party, and whether it votes
for it by itself), `POST /events` (an event, whoever signed it), `GET /events/{id}`,