Agent identity

The credential lifecycle

  1. Register — the agent is assigned a UUID.
  2. Provision — 32 random bytes, hex-encoded. The raw value is returned once, at provisioning only.
  3. Store — what is persisted is a salted PBKDF2 hash with a server-side pepper. The raw secret is never stored.
  4. Verify — a constant-time comparison. A rejected credential leaks no timing information.
  5. Rotate — the stored hash is replaced immediately. Rotation is a cutover, not a grace period: the previous credential is not retained for parallel validation.
  6. Revoke — the agent’s state flips, so its credential stops verifying.

Sessions

Session tokens are JWTs signed with HS256, carrying extended claims:

ClaimPurpose
trustDomainThe boundary the session is valid in
blastRadiusHow far the session’s authority extends
sessionIdServer-side session handle
executionContextThe context the call is made in

What this is not

Not key-bound identity AWARE authenticates the holder of a shared secret. There is no asymmetric key pair, no X.509 certificate and no SPIFFE identifier. A bearer secret is replayable by anything that obtains it; short-lived sessions, revocation and blast-radius scoring reduce that exposure, but they do not eliminate it.