Agent identity
The credential lifecycle
- Register — the agent is assigned a UUID.
- Provision — 32 random bytes, hex-encoded. The raw value is returned once, at provisioning only.
- Store — what is persisted is a salted PBKDF2 hash with a server-side pepper. The raw secret is never stored.
- Verify — a constant-time comparison. A rejected credential leaks no timing information.
- Rotate — the stored hash is replaced immediately. Rotation is a cutover, not a grace period: the previous credential is not retained for parallel validation.
- Revoke — the agent’s state flips, so its credential stops verifying.
Sessions
Session tokens are JWTs signed with HS256, carrying extended claims:
| Claim | Purpose |
|---|---|
trustDomain | The boundary the session is valid in |
blastRadius | How far the session’s authority extends |
sessionId | Server-side session handle |
executionContext | The 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.