diff options
| author | tv <tv@krebsco.de> | 2026-11-19 20:12:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 21:27:49 +0100 |
| commit | b827ecbfff930790af45b04b8e6f01e4f5514e75 (patch) | |
| tree | 2f9669fb9f9494e12c4dbe33d06196ec3a97e620 /docs | |
| parent | 9bf334bedbc4b0cc3ce32fcd3baef27d3072f194 (diff) | |
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.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/configuration.md | 6 | ||||
| -rw-r--r-- | docs/guides/federation/running-a-node.md | 3 |
2 files changed, 8 insertions, 1 deletions
diff --git a/docs/configuration.md b/docs/configuration.md index 56c3347..ea401f5 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -272,6 +272,12 @@ continuum-party --federation krebs --node http://tv:secret@localhost:3000 \ continuum-party vote 8d02 yes # krebs, the only one ``` +Where `node` names no user and no `token` is given, the client logs in to the node as its +party, by `key`, where the federated node takes it: a party's session, which reads and +puts events and nothing else ([`guides/federation/running-a-node.md`](guides/federation/running-a-node.md), +[Its API](guides/federation/running-a-node.md#its-api)). So `node = "https://node.example"` +and a key whose party a version names are all a party's people need. + `key` is an OpenSSH private key file, or a public key an ssh-agent holds: the key itself (`key = "ecdsa-sha2-nistp256 AAAA…"`), or a file of such lines, whose first signs ([`guides/federation/keys.md`](guides/federation/keys.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}`, |
