diff options
| author | tv <tv@krebsco.de> | 2026-11-19 20:11:05 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 21:27:21 +0100 |
| commit | 9bf334bedbc4b0cc3ce32fcd3baef27d3072f194 (patch) | |
| tree | 6236db6799c2523ccdb899e6a42cc2153ce4eb08 /src/simtest/remakes.rs | |
| parent | fc6c7101cdb42666c1f79df4206029c7cf7e61c6 (diff) | |
federated nodes: a party's keys log in as the party, for federation work
A party's people work with the federation by signing as the party, with
a key of its set; what they need of a node is to read and to put events,
which a node's users, its operators, may do with every power besides.
POST /auth/login/party takes a challenge (POST /auth/challenge) signed
with one of the keys that sign for the party (fold::State::signing_keys:
those its current version names, and its key set as it counts), for the
namespace continuum-login, armored or as the federation spells a
signature (keys::signer, keys::verifies_in: the federation's checks, but
for the namespace), and answers a token as the party. Logins by key are
counted per party as per user (challenge::take_with, shared with
logging in by a registry's keys).
The token names the key (Claims::party). Such a session does federation
work alone (api::access::federated): what --store-readers do, and
POST /events; anything else is 403. Every request checks that the key
still signs for the party: once a version or the party's key set drops
it, 401. A build from before reads no token naming a key, as its claims
deny fields they don't know, so never takes a party's session for a
user's; and only the node that issued it takes it, as every token in a
federated swarm.
Diffstat (limited to 'src/simtest/remakes.rs')
0 files changed, 0 insertions, 0 deletions
