All Classes and Interfaces
Class
Description
Janssen Project configuration
How a producer chain comes to exist (design §8).
Reads
contextInformation as a flat string map.Base interface for all Jans Auth configurations
gRPC server configuration
Health Entry for audit logging.
Response body of the producer-chain listing admin endpoint.
Admin request body to pre-register a producer chain (design §8).
A registered producer chain as returned by the admin API (design §8).
Response body of the producer-key listing admin endpoint.
Admin request body to register a producer's Ed25519 verification key (design §6).
A registered producer key as returned by the admin API.
Admin request body to revoke a producer's Ed25519 verification key.
Telemetry Entry for audit logging.
The
POST /audit/trace success body (design §11.1): the identity and
receipt position the record was accepted at, plus the four ingestion flags fixed at ingestion
time.The
POST /audit/trace/bulk response body (design §11.2): one
TraceBulkResultEntry per submitted array element, in request order.One element of
POST /audit/trace/bulk's results array (design §11.2): the submitted array's position and whether that item was accepted.A registered producer chain (design §8).
Binds an OAuth client to a TRACE evidence domain and the producer ids it may submit records for.
TRACE evidence-ingestion configuration: evidence-domain bindings, lateness policy and request
limits .
Swagger schema for the structured TRACE error body.
The direct TRACE records of one execution, ordered by receipt sequence (design §10, §11.3).
The Lock-derived ingestion flags shared by the acceptance response and the
ingestion
member of a record envelope.The
ingestion member of a TRACE record envelope (design §10): the
receipt-chain position and the four Lock-derived flags (eventually consistent).A policy store archive release some Lock node has served, shared by every node.
A registered producer Ed25519 key (design §6).
A receipt-chain position allocation claim (design §9).
State of a TRACE receipt-chain position allocation claim (design §9).
One accepted TRACE record (design §10).
A single TRACE record envelope (design §10, §11.2): the stored assertion plus
the verification outcome and the Lock-derived ingestion metadata.
TRACE records matching a policy store release search, ordered by receipt sequence.
Signature verification outcome stored alongside a TRACE record (design §10).
The
verification member of a TRACE record envelope (design §10).