Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: a banned node exits when it loses its routers, not on refresh
Tomas Tormo2dab058c3ccd
diff --git a/site/content/docs/concepts/identity.md b/site/content/docs/concepts/identity.mdindex 26043a28..458a16ec 100644--- a/site/content/docs/concepts/identity.md+++ b/site/content/docs/concepts/identity.md@@ -257,8 +257,11 @@ Revocation operates at two levels:1. **Mesh-wide node, identity, and root-prefix Biscuit revocation:**`POST /admin/revoke` with a peer ID (or `agentmesh-one admin ban`, or the console)- marks the node as banned. Its next refresh is refused and the node daemon- exits. The control plane publishes banned peer IDs in `/info` and+ marks the node as banned. Routers and peers drop the node as soon as the+ ban event reaches them. The control plane refuses the node's next refresh,+ but the node keeps its current credential. The daemon exits when its+ connection monitor fails three router checks in a row, one minute apart by+ default. The control plane publishes banned peer IDs in `/info` and`GET /revocations`, together with revoked root Biscuit revocation IDs(`RevocationIds()[0]`). Because every offline-attenuated child Biscuitshares the root authority block's `RevocationIds()[0]`, revoking the rootdiff --git a/site/content/docs/guides/headless-enrollment.md b/site/content/docs/guides/headless-enrollment.mdindex fe61388f..7bc2e376 100644--- a/site/content/docs/guides/headless-enrollment.md+++ b/site/content/docs/guides/headless-enrollment.md@@ -255,7 +255,8 @@ curl -fsS -X POST https://mesh.example.com/admin/revoke \-d '{"peer_id":"12D3KooW…"}'```-The node's next refresh fails and its daemon exits. Connected peers drop it-as soon as the ban event reaches them. `POST /admin/nodes/<peer-id>/unban`,+Routers and connected peers drop the node as soon as the ban event reaches+them. Its next refresh fails. The daemon exits once the node cannot reach a+router for three checks in a row. `POST /admin/nodes/<peer-id>/unban`,or **Restore** in the console's Revoked Nodes list, reverses the ban. `agentmesh-control-plane admin ban --peer <id>` and `unban` dothe same directly in the database, for cases where the API is not reachable.