Actions
Feature #272
open
Epic #49: Implement user, groups and permissions management
Agent identity
Feature #272:
Agent identity
Start date:
Due date:
% Done:
0%
Estimated time:
(Total: 0:00 h)
Description
A node that runs game servers must prove it is a node this installation enrolled, and an operator must be able to cut one off when it is decommissioned or compromised. Agents carry out work the control plane hands them; they never judge what a person is allowed to do.
An administrator enrols a node by generating a short-lived, single-use token. The node presents it once, receives its own lasting credential, and uses that from then on. Credentials are listable, can be rotated, and can be revoked one node at a time.
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions