From b827ecbfff930790af45b04b8e6f01e4f5514e75 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 20:12:39 +0000 Subject: continuum-party: logs in as its party by its key, with no user of the node Where --node names no user and no --token is given, the client logs in to the node as its party (Node::log_in): a challenge, signed with --key (a file's, or through the ssh-agent) for continuum-login, for POST /auth/login/party, whose token goes with every request then. The party is the one its record names, or, for `init`, the one it begins a record of. A party's people need a node's address and a key of their party's, nothing of its operator's. --- docs/guides/federation/running-a-node.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/guides/federation/running-a-node.md') diff --git a/docs/guides/federation/running-a-node.md b/docs/guides/federation/running-a-node.md index ea51f8a..44b309a 100644 --- a/docs/guides/federation/running-a-node.md +++ b/docs/guides/federation/running-a-node.md @@ -79,7 +79,8 @@ alone, so that a party listing many nodes can't be all of a node's neighbours. (`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. + powers. `continuum-party` logs in so by itself, where `--node` names no user and no + `--token` is given, as the party its record names. * **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}`, -- cgit v1.3.1