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/configuration.md | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/configuration.md') 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), -- cgit v1.3.1