Identity and Token Model
Every request the HYPR AgentPass™ gateway forwards is attributable to one of three identities. Knowing which one a request carries tells you who is accountable for it, and what it may reach.
| Identity | Proves | Issued when | Reaches | Managed in |
|---|---|---|---|---|
| Agent identity | The request came from a specific, named agent that a specific person is accountable for | An agent is created or synced from a provider, or a service agent is created | The connectors the agent is scoped to, with the tools its role permits: its owner's role, or a service agent's own role | Agent Identity |
| Supervisor identity | The person signed in to AgentPass is the one behind this agent | The supervisor signs in, to the console, the Agent Portal or an agent's channel, and the agent uses that identity directly | Whatever the supervisor's role permits | Supervisor Identity |
| On behalf of a supervisor | A person authorized this agent to act for them on a named tool, within a bounded session | The supervisor authorizes a connection once. The gateway issues the agent a scoped session token, and keeps the underlying credential itself | Only the authorized tool, for as long as the grant is valid | On Behalf of a Supervisor |
Agent Identity
An agent is a first-class identity, not a property of a person. AgentPass assigns it a credential of its own, and records its owner. When the agent was synced from a provider, AgentPass keeps its identity in step with that provider.
An agent with no owner cannot exist. A service agent, one that runs with nobody at the keyboard, follows the same model, with an accountable owner named when it is created.
Supervisor Identity
A supervisor authenticates to AgentPass through your identity provider. An agent can act with that identity directly, such as a coding agent on the supervisor's own workstation. The request is then attributed to the supervisor, and the supervisor's role decides which tools the agent is offered and may call.
Roles arrive from your identity provider, or are assigned in the console. See Roles and Permissions.
On Behalf of a Supervisor
When a tool is protected by its own sign-in, the agent never holds that credential:
- The supervisor authorizes the connection once.
- The gateway stores the resulting credential.
- The agent receives a scoped session token, good for that tool and nothing else.
Revoking the grant, or letting it expire, cuts the agent off without touching the supervisor's own access.
Decisions Bound to a Person
Two decisions on the request path are made by a person, and bound to them:
- Approving an agent's first connection
- Approving an action a policy holds
Both are answered on the HYPR mobile app or in the console, and the record shows who answered. With Require signed approvals set to Required (production), every approval carries the supervisor's passkey signature, so the record proves which person approved which action. Connect to Your HYPR Tenant covers connecting the gateway to your HYPR tenant for this.
Related
- Identity — configure each identity
- Architecture: The Request Path — where identity sits on the path
- Approving and Denying Agent Actions — what a passkey-bound approval looks like to the supervisor