The edge-node local dashboard (auth'd, port 80) has no credentials management. When an admin uses Reissue key (POST /nodes/{id}/reissue-key) on the C2 side, the only way to get the new key onto the node is: SSH in, edit configs/credentials.json, docker compose restart edge-node.
An operator resetting a fleet (changing servers, rotating creds) has to do this by hand on every box.
Ask: a small authenticated page/section on the node dashboard to paste a reissued api_key (and ideally the C2 URL / broker host), write configs/credentials.json, and bounce the MQTT connection without a container restart.
Related: this is the same configs/credentials.json that install.sh §5 writes at first boot. The proper end state is the edge-node app owning its own enrollment + credential lifecycle (see node-26#4 follow-ups), of which this is the manual-override half.
The edge-node local dashboard (auth'd, port 80) has no credentials management. When an admin uses **Reissue key** (`POST /nodes/{id}/reissue-key`) on the C2 side, the only way to get the new key onto the node is: SSH in, edit `configs/credentials.json`, `docker compose restart edge-node`.
An operator resetting a fleet (changing servers, rotating creds) has to do this by hand on every box.
**Ask:** a small authenticated page/section on the node dashboard to paste a reissued api_key (and ideally the C2 URL / broker host), write `configs/credentials.json`, and bounce the MQTT connection without a container restart.
Related: this is the same `configs/credentials.json` that `install.sh` §5 writes at first boot. The proper end state is the edge-node app owning its own enrollment + credential lifecycle (see node-26#4 follow-ups), of which this is the manual-override half.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The edge-node local dashboard (auth'd, port 80) has no credentials management. When an admin uses Reissue key (
POST /nodes/{id}/reissue-key) on the C2 side, the only way to get the new key onto the node is: SSH in, editconfigs/credentials.json,docker compose restart edge-node.An operator resetting a fleet (changing servers, rotating creds) has to do this by hand on every box.
Ask: a small authenticated page/section on the node dashboard to paste a reissued api_key (and ideally the C2 URL / broker host), write
configs/credentials.json, and bounce the MQTT connection without a container restart.Related: this is the same
configs/credentials.jsonthatinstall.sh§5 writes at first boot. The proper end state is the edge-node app owning its own enrollment + credential lifecycle (see node-26#4 follow-ups), of which this is the manual-override half.