Package com.revetsec
@NullMarked
package com.revetsec
Revetsec's root package: the types shared by every protocol package, such as the exception root, error
categories, sealed pending-state support and the outbound URI policy.
It contains nothing protocol-specific, and it depends on no other exported Revetsec package. Its implementation
uses the internal packages that serve it, such as com.revetsec.internal, which never appear in its public
signatures.
- Author:
- Mark Allen
-
ClassDescriptionBounded application-held correlation secret for browser pending workflows.Checks browser request metadata against exact configured origins.Mutable, non-thread-safe browser-origin policy configuration.Closed outcome of a browser request-origin check.An admitted request.The input that admitted a request.A fixed rejection reason.A request rejected before application state changes.Fixed, value-free codes for a builder's configuration shape.The broad kind of failure a
RevetsecExceptionreports.Thrown when a sealed value cannot be opened.A fixed-diagnostic key import or explicit pair-check failure.Fixed reasons; later versions may add reasons, so application switches need a default branch.Bounded imports of ordinary JCA key material: RSA (2048 through 16384 bits, the existing exponent/ROCA policy), EC P-256/P-384 and canonical, non-small-order Ed25519 public points.Bounded application-held correlation secret for selected WebAuthn and TOTP operations.Decides which URIs Revetsec may send requests to.The root of every exception Revetsec throws for a condition that a remote party, the input or the runtime environment can cause.A secret key forStateSealer, with its key ID.Seals short strings into opaque, URL- and cookie-safe values that only a holder of the same keys can open, and only for the same context before they expire.Builds aStateSealer.The outcome of opening sealed application state.The state could not be opened.The state authenticated for the context and its lifetime has not ended.Immutable identities of an authority and its active data/recovery admission.Immutable factual validation timing and optional timing after known durable acknowledgement.An engine-created exact time predicate, inspected by the backend inside its final atomic context.A backend's immutable time statement, bound to the active data/recovery admission.An admitted UTC observation with a fixed generation profile.Time is unavailable while the authority/data admission metadata remains obtainable.