Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
docs: mesh:system:authenticated matches every valid credential
Tomas Tormo319bdfe31370
diff --git a/site/content/docs/concepts/authorization.md b/site/content/docs/concepts/authorization.mdindex 6ae5dd38..1de2d3d1 100644--- a/site/content/docs/concepts/authorization.md+++ b/site/content/docs/concepts/authorization.md@@ -90,10 +90,11 @@ from a file (`--policy-file`).A member is one of: `user:`, `email:`, `group:` or `idp_role:` followed by avalue from the identity's OIDC claims; `node:` followed by a peer ID; or the-special value `mesh:system:authenticated`, which matches every identity that-the identity provider authenticates. Be careful with the last one. On a-public identity provider it means everyone, so bind it only to roles with-few grants.+special value `mesh:system:authenticated`, which matches every holder of a+valid credential. That includes members that enrolled with a bootstrap token+and delegated sessions, not only the identities that the identity provider+authenticates. Be careful with this member. On a public identity provider+it means everyone, so bind it only to roles with few grants.Roles are never members and never claims. `role:x` is not a valid member,and an identity provider cannot give out a mesh role by putting it in adiff --git a/site/content/docs/reference/policy.md b/site/content/docs/reference/policy.mdindex ec6c85f6..12b5f8b4 100644--- a/site/content/docs/reference/policy.md+++ b/site/content/docs/reference/policy.md@@ -223,7 +223,7 @@ A member is one of:| `group:<name>` | an entry of the `groups` claim || `idp_role:<name>` | an entry of the issuer's `roles` claim || `node:<peer-id>` | one node, by key (exact peer ID only; wildcards are not permitted on `node:`) |-| `mesh:system:authenticated` | every identity that the identity provider authenticates |+| `mesh:system:authenticated` | every holder of a valid credential, including members enrolled with a bootstrap token and delegated sessions |Each claim-backed member (`user:`, `email:`, `group:`, `idp_role:`) may carrya single trailing `*` (prefix match, compiled to `$v.starts_with("<prefix>")`)@@ -241,9 +241,9 @@ and UTF-8 (for example `group:Engineering Team`), and may not contain `"`,`\`, or control characters.`role:` is not a member, because a role cannot grant a role. A bootstrap-token enrollment carries no OIDC claims. Such a node receives exactly the-token's role and nothing that a binding on claims would add, so the grants-must be on the role itself.+token enrollment carries no OIDC claims. Such a node receives the token's+role and the roles bound to `mesh:system:authenticated` or to its+`node:<peer-id>`. A binding on claims adds nothing to such a node.## Egress destinations