Skip to content

me.connections.grant answers an assertion, not a token

Decision 375 · accepted · 2026-09-15

A short-lived key manager token scoped to the caller's own slot would be a token the plane minted, a token the plane minted is a token the plane held, and a plane that held one could have read the slot. So it answers the assertion instead — a signed statement of who the caller is, which the plane is entitled to make because it is the thing that authenticated them — and the client exchanges that with the key manager itself.

The same mechanism a pod uses, which is the argument for it: there is one way to become a person at the key manager, and the plane is on neither side of it.

Governs: apps/troupe_plane/lib/troupe/plane/harness.ex