Skip to main content

Capabilities overview

This section documents every capability TrustPlane Auth ships today, one page each, in the same shape: Concept → Implementation → Example. Nothing here is aspirational — each maps to real code, a real CLI command, or a real make target.

The capability map

What each capability is, in one line

#CapabilityOne-linerPage
1Passport issue/verifyMint and locally verify a short-lived proof-bound artifact
2Request bindingBind a passport to this exact request with transcript-v1
3Replay protectionConsume each jti once, atomically (memory or Redis)
4Bundle policy & freshnessPer-route rules + fail-closed staleness from a local bundle
5Signed bundle lifecycleSign, verify, refresh, and remove trust/policy material safely
6Trust anchors & allowed_sourcesAuthorize many issuers/clients per route; add clients with no redeploy
7Brownfield adapterReverse-proxy verifier in front of an unmodified API
8Broker & attested_workloadLocal issuer; optional SPIFFE/SPIRE-attested identity
9Audit eventsStable JSON record of every allow/deny decision

Capability → example mapping (quick view)

Every capability has a runnable proof. The full table with reason codes lives in the Capability → example map; here is the short version:

CapabilityTry it with
Passport issue/verifytrustplane issue + trustplane verify; make demo
Request bindingmake demo-provider-gateway; trustplane sign --curl
Replay protectionmake demo-provider-gateway (duplicate → jti_replay)
Bundle policy & freshnesstrustplane bundle build; make demo-provider-gateway
Signed bundle lifecycletrustplane bundle sign; trustplane bundle verify; trustplane bundle remove-source
Trust anchors & mergetrustplane bundle merge-source; multi-anchor fixture
Brownfield adaptermake demo-adapter (valid / 401 / 403)
Broker & attested_workloadtrustplane broker issue; trustplane up; SPIRE M2M smoke
Audit eventsemitted by broker/verifier/adapter decisions

A note on scope

These capabilities are the v0.1 boundary — a local product-readiness contract, gated by make v01-acceptance. Deployment of the adapter is covered separately under Deployment overview, and uses these same capabilities unchanged. See the v0.1 boundary for exactly what is in and out of scope.