pub struct SessionContextInputs {
pub verifier_id: String,
pub workspace_id: String,
pub agent_id: String,
pub session_id: String,
pub invocation_id: String,
pub request_hash: Vec<u8>,
}Expand description
The inputs that identify the session a presentation belongs to, plus
the request_hash binding the specific operation (SPEC §6.4.9). The
Middleware Custody Profile (SPEC §15.2.1) requires all of them; other
deployments populate what they have.
Fields§
§verifier_id: StringThe verifier’s identity (e.g. its public key ID). Including it makes cross-verifier challenge forwarding detectable at the cryptographic layer (SPEC §15.1).
workspace_id: StringThe deployment’s workspace/tenant identifier.
agent_id: StringThe presenting agent’s identity.
session_id: StringThe session identifier.
invocation_id: StringThe specific invocation within the session.
request_hash: Vec<u8>Exactly 32 bytes — the operation_context_hash of the action
being authorized. A deployment with no operation-specific inputs
derives it from an all-empty OperationContext. Binding the
session but not the operation would let an intermediary attach a
valid proof to the wrong action inside the right session.