All Classes and Interfaces
Class
Description
A raw access token returned by an AS.
The outcome of a cached client-credentials token acquisition.
The endpoint returned a non-transient client error.
The source returned a currently valid access token, from its cache or a completed renewal.
Explicit access-token interoperability modes.
Caller-thread resource events and inherited OAuth/JOSE events, without credentials or claims.
A local bearer credential verdict, with fixed reasons and no token, claims or lower-layer exception retained.
The failed credential check.
The access-token verdict.
The credential was rejected; no identity, claims, credential or exception is retained.
The introspection endpoint rejected the request with a checked, nontransient client error.
All configured access-token checks passed.
Validates bearer access tokens for explicitly configured audiences.
Argon2id version 19 parameters for newly created password hashes.
The outcome of OAuth callback completion.
A bound callback reported access_denied after all pending-state and issuer checks.
The pending store did not complete its operation.
A local callback or pending-state security check rejected completion.
A bound callback reported an authorization error after all pending-state and issuer checks passed.
The endpoint returned a non-transient client error.
The authorization flow completed once and returned endpoint tokens.
A browser authorization error, reported only after pending-state and issuer checks pass.
A browser redirect and its pending authorization.
Per-authorization options.
Mutable request-option builder.
The trusted callback delivery mode.
A parsed browser authorization response.
The outcome of parsing a raw, unverified OAuth browser callback.
A malformed, duplicate, oversized or split-channel callback.
A syntactically parsed callback that remains unverified until transaction completion.
Known authorization-server metadata.
Builds manually configured metadata.
The outcome of parsing bounded provider metadata.
A rejected metadata document with no received payload.
Checked metadata; the application still selects a trusted issuer.
A bounded WWW-Authenticate Bearer value (RFC 6750 section 3 and RFC 9728 section 5).
Mutable challenge configuration.
RFC 6750 section 3.1 bearer errors and their recommended HTTP status codes.
An unverified credential parsed from exactly one Authorization field (RFC 6750 section 2.1).
The outcome of parsing materialized Authorization headers.
No Authorization header was supplied.
The supplied header values are malformed, duplicated or oversized.
Exactly one header supplied a syntactically valid, unverified bearer credential.
Bounded 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.
The sole audience of an OAuth client assertion.
Supplies one immutable key and header snapshot per assertion POST.
Immutable signer and protected-header identifiers selected together for one assertion.
Configures one immutable signing snapshot without provider or signing calls.
One OAuth client authentication strategy.
Configures assertion audience and lifetime.
A bounded caller-thread cache for confidential client-credentials access tokens.
Configures a source without network I/O.
Client-secret Basic encoding.
Fixed, value-free codes for a builder's configuration shape.
The broad kind of failure a
RevetsecException reports.An ID token whose signature, registered claims and OIDC checks have all passed.
Bounded single-process optional cache with timed interruptible locking and approximate LRU
eviction.
A bounded, single-process pending-authorization store.
Configures the store.
Bounded, process-local store for pending SAML login and logout with atomic single consumption.
Bounded, process-local SAML assertion replay cache.
Explicit bounded, volatile, single-process TOTP demonstration store.
Caller-thread configuration for explicit volatile storage.
Explicit bounded, volatile, single-process WebAuthn store.
Thrown when a sealed value cannot be opened.
Whether the RFC 9207 callback issuer is required.
A rejected JOSE input: a token that
JwtValidator refused, or a JSON Web Key Set document that
Jwks.fromJsonResult(String) rejected.Why a JOSE input was rejected.
Receives events from
JwtValidator and RemoteJwksSource, for metrics, logs and alerts.A JSON array: an ordered, unmodifiable list of values.
A JSON
true or false.The JSON
null.A JSON number, held exactly as a
BigDecimal.A JSON object: an unmodifiable map from member names to values that keeps the order in which members were added.
Builds a
JsonObject one member at a time, keeping the order in which members are added.A JSON string.
An immutable JSON value (RFC 8259): exactly one of
JsonObject, JsonArray, JsonString,
JsonNumber, JsonBoolean or JsonNull.One usable public key from a
Jwks: an RSA, EC (P-256, P-384 or P-521) or Ed25519 key that passed
every rule for verifying JWS signatures (see JwkSkipReason).A JSON Web Key Set (RFC 7517 section 5): the usable public verification keys of a key set document, in document
order.
Why a key in a JSON Web Key Set is not used.
The outcome of parsing a JSON Web Key Set document with the default size and key-count limits.
The input was rejected; this variant contains only a fixed reason.
A JSON Web Key Set document passed the structural and resource-limit checks.
Publishes an immutable snapshot of public verification keys without an OAuth authorization server, signing,
storage, network access or background threads.
Configures an immutable public key snapshot.
An immutable HTTP response containing only public JWKS data.
Where a validator gets the public keys that verify token signatures: a fixed key set
(
StaticJwksSource) or one fetched from a URI and kept up to date (RemoteJwksSource).Thrown when a
RemoteJwksSource has no usable JSON Web Key Set for a call: the fetch failed, a
recent failure is still suppressing fetches, the limit of two requests per cooldown held the call back, or the
call's deadline ended while it waited for another caller's fetch.A JWS signature algorithm, named by its
alg header value (RFC 7515 section 4.1.1, RFC 7518 section 3.1,
RFC 8037 section 3.1 and RFC 9864).Signs compact JWS credentials with one application-owned key pair and one fixed algorithm.
Configures one signing operation.
A failure to sign with an application-owned RSA key, or to verify the signature before releasing it.
Why signing failed.
A JWT that
JwtValidator.validateResult(String) accepted: its signature verified with a trusted key, and its type,
issuer, audience, lifetime and required claims passed.RFC9068 JWT bearer-access-token validator for exact issuer and explicitly configured audiences.
Configures an immutable resource validator.
The claims of a validated JWT (RFC 7519 section 4).
An immutable JWT claims set for signing (RFC 7519 section 4), with typed registered claims and JSON custom claims.
Builds an outbound claims set.
Immutable protected-header metadata for signing a JWT: its required
type and optional key
identifier and SHA-256 certificate thumbprint.Configures an immutable JWT signing header without signing or I/O.
A supported JWT protected-header
typ value used when signing a token.Thrown when a well-formed token fails a check: its algorithm, key, signature, type, issuer, audience, lifetime,
required claims or confirmation claim.
The outcome of JWT validation.
The input was rejected; this variant contains only a fixed reason.
A JWT passed all configured signature, header and claims checks.
Validates JWTs in the JWS compact serialization (RFC 7519, RFC 7515) signed with a public key, for one expected
issuer.
Builds a
JwtValidator.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.
Exact historical character preparation for an explicitly selected legacy verifier.
Thrown when a token or a JSON Web Key Set document cannot be parsed, or exceeds a limit.
Trusted application authorization decision; it is not a verified authentication or token proof.
Replacing decision builder.
A library-created outcome.
The library-created Completed outcome.
The library-created Denied outcome.
The library-created InteractionRequired outcome.
A fixed rejection with no proof, request, credential, identity, claims or exception object.
Caller-thread OAuth code issuer with authoritative online grant status.
Mutable, non-thread-safe issuer configuration.
Application-owned authoritative issuer persistence.
OAuth 2.0 authorization-code, client-credentials, refresh and revocation client.
Configures an OAuth client.
Trusted bounded address resolution for opt-in client metadata retrieval.
Thread-safe storage for bounded encrypted client-metadata carriers.
Immutable bounded encrypted cache carrier.
Fixed-diagnostic optional-cache failure, distinct from a miss or comparison conflict.
The optional-cache failure reasons.
Bounded opaque address for optional client-metadata storage.
Immutable opt-in configuration for public client metadata documents.
Builds an enabled policy; null property values reset defaults, except resolver and cache null
clear required properties.
Application-owned verification of a pre-registered confidential client's secret.
A fixed, cause-free failure of configured assertion keys, signing, endpoint trust, discovery identity or issuer policy.
An OAuth endpoint category used in redacted observer events.
Fixed OAuth and OpenID Connect protocol errors for endpoint and checked authorization rejections.
A token, revocation or UserInfo endpoint error.
An OAuth request, response, validation or transport failure.
Reasons for OAuth failures.
Issuer-created grant facts supplied to the application's continuing authorization policy.
Continuing application authorization policy, invoked outside store transactions at approval, code exchange
and refresh.
A library-created outcome.
A fixed rejection with no proof, request, credential, identity, claims or exception object.
The library-created Succeeded outcome.
A library-created outcome.
A fixed rejection with no proof, request, credential, identity, claims or exception object.
The library-created Succeeded outcome.
Trusted application-owned durable key lifecycle and distribution callback.
Immutable application declaration of active, published and retained public keys.
Builds a checked immutable declaration without signing or provider lookup.
One application-owned RS256 signing key.
Receives synchronous, caller-thread OAuth events.
An authorization-server response is malformed or redirected.
The outcome of one token revocation request.
A library-created outcome.
The endpoint returned a non-transient client error.
A fixed rejection with no proof, request, credential, identity, claims or exception object.
The endpoint accepted the revocation request; RFC 7009 also accepts unknown tokens.
The library-created Succeeded outcome.
Trusted registered-client authentication policy: public authentication or confidential client_secret_basic.
Immutable application-owned client registration.
Replacing, snapshotting registration builder.
Application-owned lookup of trusted, pre-registered client configuration.
A fixed configuration failure in issuer processing; construction is restricted to Revetsec.
The sealed issuer exception family.
Fixed classifications; a later release may add values.
A restricted view of a checked, pending browser interaction.
Safe synchronous caller-thread issuer events.
Fixed operation kinds, without request or application data.
An immutable, bounded response prepared by the authorization server.
A fixed signing failure in issuer processing; construction is restricted to Revetsec.
A fixed store failure in issuer processing; construction is restricted to Revetsec.
A fixed transport failure in issuer processing; construction is restricted to Revetsec.
A fixed validation failure in issuer processing; construction is restricted to Revetsec.
Immutable factual issuer commitment, definitive refusal or uncertainty.
Outcome of an atomic, durable issuer store commit.
Immutable encrypted persistence carrier, not an authenticated authorization proof.
Opaque issuer storage address.
Issuer storage record kinds; a later release may add values.
Coherent linearizable issuer entry/absence and admitted time metadata.
The exact requested address, entry/absence and metadata from one atomic observation.
The requested recovery/data incarnation cannot be served.
No coherent authoritative observation could be established.
Complete immutable issuer transaction, created only by the engine.
An exact version or ABSENT predicate, engine-created and checked atomically with every other predicate.
An engine-created PUT or REMOVE; PUT carries its exact key-matched entry and REMOVE carries no entry.
The two mutation operations.
The two explicit transaction modes.
The outcome of one token request.
The endpoint returned a non-transient client error.
The endpoint issued tokens.
A library-created outcome.
A fixed rejection with no proof, request, credential, identity, claims or exception object.
The library-created Succeeded outcome.
A network failure, interruption, attempt-limit hold or unavailable HTTP client.
A pending authorization or OAuth security check failed.
One fully validated code-flow authentication.
Per-login OIDC options (OpenID Connect Core section 3.1.2.1).
Mutable per-login option builder.
The outcome of OIDC callback completion.
A bound callback reported access_denied after all pending-state and issuer checks.
The pending store did not complete its operation.
A local callback or pending-state security check failed.
A bound callback reported an authorization error after all pending-state and issuer checks passed.
The endpoint returned a non-transient client error.
The ID token failed validation.
The shared authorization checks and all ID-token profile checks passed.
OpenID Connect authorization-code relying party.
Mutable OIDC client configuration.
Explicit per-client OIDC relaxations.
An OpenID Connect validation failure.
Exact issuer validation or the fixed Microsoft Entra common/organizations v2.0 trust policy.
A fixed configuration, preparation, storage or runtime failure in RP-Initiated Logout.
Fixed reasons.
An explicitly retained logout credential bound to the original OIDC continuity reference.
Structure-only restoration of a logout credential from trusted or typed sealed storage.
A structurally consistent hint, not an authentication proof.
A stored form could not be opened or structurally restored.
A prepared browser request, not provider-session termination or authenticated identity.
A correlated browser return or fixed rejection.
Value-free callback rejection reasons.
The callback did not satisfy the selected correlation profile.
Correlation succeeded.
Receives caller-thread OIDC events and the inherited OAuth/JOSE endpoint events.
OpenID provider metadata (OpenID Connect Discovery 1.0 section 3), from discovery or explicit configuration.
Mutable explicit provider configuration.
The outcome of parsing bounded provider metadata.
A rejected metadata document with no received payload.
Checked metadata; the application still selects a trusted issuer.
Checked values from one refresh, released after any returned ID token passes signature, profile and original-session
continuity checks.
The result of an OIDC token refresh.
A local OIDC check rejected the operation.
The endpoint returned a non-transient client error.
The refresh completed and any returned ID token passed continuity checks.
Continuity reference for refresh and future logout.
The outcome of parsing a stored OIDC continuity reference.
The stored reference could not be parsed or opened.
A structurally valid continuity reference was parsed.
UserInfo whose subject exactly matches a verified authentication.
The outcome of a UserInfo request.
A local OIDC check rejected the operation.
The endpoint returned a non-transient client error.
The UserInfo response passed all configured identity and profile checks.
An ID token, UserInfo response or refresh continuity check failed.
Fixed OIDC validation reasons.
Bounded application-held correlation secret for selected WebAuthn and TOTP operations.
Decides which URIs Revetsec may send requests to.
A generated password verifier.
Standalone, caller-thread password hashing.
Mutable configuration helper.
Complete result of generating a new password hash.
Input was refused without hashing.
A new hash is ready for application-owned persistence.
Work or a required dependency was unavailable; no hash was generated.
An application-owned, 32-byte Argon2id secret-input key identified by a non-secret ID.
Coherent active and retained pepper keys for one operation.
Snapshot construction; keys are never exposed by iteration.
Application pepper-source outcome.
Coherent key snapshot is available.
The provider could not supply its current snapshot.
Thread-safe application source of coherent pepper-key snapshots.
Fixed internal reasons for a refused password-hashing or verification request.
Operational reasons for password work that could not be completed.
Input and stored-cost ceilings applied around admitted password preparation/KDF work.
Mutable construction helper; no cryptographic or provider work runs during construction.
Complete local password-verification result.
The submitted complete password matched the selected stored verifier.
The submitted password did not match.
An input or stored verifier was invalid or unsupported under this operation.
Work or a required dependency was unavailable; no password match was established.
Explicit in-memory, process-local admission for expensive password work.
Supported verify-only PBKDF2 pseudorandom functions for trusted legacy records.
One pending browser authorization, including secret state, PKCE verifier and an OIDC nonce slot.
Closed, value-free provider outcomes for saving a browser-bound pending authorization.
A browser-bound source for completing one authorization.
Storage for opaque, browser-bound pending authorization records.
A pending-authorization store could not complete an operation.
One bounded pending logout correlation record, separate from login.
A typed browser-bound source for logout return correlation.
An engine-created pending SAML login.
A sealed pending login obtained from the initiating browser's cookie.
Atomic storage for browser-bound SAML login and logout attempts.
Engine-created pending SP logout.
Browser-bound source of one SP-initiated pending logout.
Application-configured protected-resource metadata (RFC 9728 sections 2 and 3).
Mutable metadata configuration.
An immutable public signing key for publication in a JSON Web Key Set (RFC 7517).
Configures an immutable published public key.
Atomic recovery-code batch replacement for an approved current factor and batch.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
Infrastructure or recovery admission was unavailable; no success is established.
A newly committed recovery-code batch; plaintext codes cannot be retrieved again from durable storage.
Library-created proof of committed recovery-code consumption; apply a separate recovery-session policy.
Recovery-code consumption; only Succeeded carries committed recovery-method proof.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
The durable shared account admission limit prevented this attempt.
Infrastructure or recovery admission was unavailable; no success is established.
A secret refresh token.
A JSON Web Key Set fetched from a URI and cached, such as an OpenID provider's
jwks_uri.Builds a
RemoteJwksSource.The root of every exception Revetsec throws for a condition that a remote party, the input or the runtime
environment can cause.
An attribute from the covered Assertion.
One checked SAML AttributeValue.
The supported shape of this value.
Identity released only after signature, request, conditions, audience and replay checks succeed.
Optional policy on an SP-initiated AuthnRequest.
Mutable options builder.
A prepared SP-initiated login, a configuration rejection, or an unavailable signing/time source.
A POST-binding request and its browser pending state.
A Redirect-binding request and the pending state that must accompany the browser.
A local configuration rejection discovered when preparing a request.
The time, randomness or signing capability was unavailable.
The result of completing an SP-initiated SAML login.
A replay mutation may have succeeded, so the caller must reconcile before retrying.
Bounded local validation reasons, with no raw input attached.
A fixed local validation rejection.
Bounded classification of a SAML non-success StatusCode.
A request-bound non-success IdP status.
A fully validated, replay-fenced authentication.
A required local capability or backend was unavailable.
Explicit per-connection SAML compatibility modes.
An RSA private key paired with its public X.509 certificate for SAML signing or decryption.
An immutable application-approved IdP connection.
Configures one trusted IdP connection.
One bounded, application-supplied SAML IdP metadata descriptor.
Result of locally parsing application-supplied IdP metadata.
One selected, structurally checked IdP descriptor.
Input was malformed, expired or unsupported.
The local parser or certificate provider was unavailable.
Result of preparing a signed outbound logout POST form.
A browser POST form with pending state to retain until the response.
Session or connection configuration is incompatible.
Randomness, clock or signing failed.
Result of preparing a signed outbound logout Redirect.
A browser Redirect with pending state to retain until the response.
Session or connection configuration is incompatible.
Randomness, clock or signing failed.
A verified IdP-initiated logout request.
Result of a signed IdP-initiated LogoutRequest.
A checked request that the application can use to locate sessions.
The replay write outcome is uncertain.
A malformed, untrusted, expired or replayed request.
A required local capability or replay store was unavailable.
Preparation result for a signed response to an IdP-initiated logout request.
A signed LogoutResponse POST form.
Request or IdP connection did not match this SP.
Clock, randomness or signing failed.
Preparation result for a signed response to an IdP-initiated logout request.
A signed LogoutResponse Redirect.
Request or IdP connection did not match this SP.
Clock, randomness or signing failed.
Result of a signed, pending-bound IdP LogoutResponse.
A pending or replay consume may have occurred.
The response was invalid, expired, unbound or replayed.
The IdP returned a verified failure or incomplete logout status.
The IdP returned a verified flat Success status, with no subordinate code.
A required local capability or replay store was unavailable.
Status chosen by the application after handling a verified logout request.
A validated NameID with its identity-significant qualifiers.
Redacted caller-thread events for SAML service-provider operations.
Fixed SAML SP operation kinds.
Fixed outcomes without protocol payloads.
Storage provider outcomes when consuming a pending SAML login or logout.
A record removed atomically.
The consume outcome cannot be determined.
No eligible live record matches the binding, handle and any consume condition.
The store failed before a mutation.
Storage provider outcomes when saving a pending login.
An opaque untrusted SAML HTTP-POST message.
The form field that carries the untrusted message.
The outcome of parsing the SAML HTTP-POST binding.
An opaque message whose XML has not yet been parsed or verified.
Bounded input and framing failures.
A fixed local rejection; no portion of the submitted message is included.
A prepared browser form for a SAML HTTP-POST authentication or logout message.
A raw-octet HTTP-Redirect binding message.
HTTP-Redirect message field kind.
Result of bounded raw-query HTTP-Redirect binding parsing.
A parsed but not yet verified Redirect message.
Malformed, duplicate, oversized or unsigned query input.
Atomic SAML assertion replay admission.
Outcomes of an atomic replay admission.
An immutable SAML 2.0 service provider for Redirect or POST login requests, POST assertion
response completion and signed Redirect or POST logout.
Mutable configuration before creating an immutable SP.
Local SP metadata publication.
Result of producing SP metadata.
Complete XML metadata from a configured signing credential.
The SP lacks a publishable signing credential or has unsupported features.
XML or certificate encoding was unavailable.
Identity and session fields from a checked assertion for later front-channel logout matching.
The outcome of opening or parsing a SAML logout continuity reference.
Fixed storage rejection categories containing no supplied data.
The supplied or opened reference has invalid structure.
The sealed state did not authenticate for this type, context, keys or lifetime.
A structurally parsed continuity reference, not authenticated identity.
The outcome of sealing SAML logout continuity fields.
A reference sealed for the requested application context and expiry.
The complete reference cannot fit the sealer's configured output limit.
The cryptographic provider could not produce a sealed value.
Stable subject identifier derived from a persistent NameID.
Immutable SCIM attribute characteristics.
Mutable, non-thread-safe definition configuration.
Immutable SCIM attribute-path syntax with an optional absolute schema URI and one optional
subattribute.
The outcome of parsing attribute-path syntax.
A fixed rejection without retained input or an exception cause.
A syntactically valid, immutable attribute path.
Bound projection with private registration provenance; never grants access.
Closed SCIM operation outcome with redacted diagnostics.
Rejected outcome.
Succeeded outcome.
Schema-bound SCIM JSON attribute types.
Immutable description of an application authentication scheme; it performs no authentication.
Mutable, non-thread-safe authentication-scheme description configuration.
SCIM filter comparison operators (RFC 7644 section 3.4.2.2).
Immutable, explicitly selected SCIM compatibility features.
Mutable, non-thread-safe complete feature-set configuration.
Explicit SCIM compatibility relaxations; no feature is selected from request content.
Closed SCIM operation outcome with redacted diagnostics.
Accepted outcome.
Rejected outcome.
Intentional Enterprise User extension view; diagnostics are redacted.
A fixed SCIM error with redacted detail.
Fixed SCIM error types and their wire spellings.
A bounded immutable SCIM filter syntax tree (RFC 7644 section 3.4.2.2).
An ordered flattened conjunction.
An attribute comparison with a JSON literal.
Negation of a grouped predicate.
An ordered flattened disjunction.
An attribute presence test.
A predicate whose relative paths refer to the same array element.
A complete filter evaluation, or a fixed rejection without a partial verdict.
A fixed rejection; no partial verdict or application failure is exposed.
A verdict after every filter clause was checked and evaluated.
Optional bounded evaluation of schema-bound, policy-approved filters against application data.
Immutable allocation and structural limits for SCIM filter syntax.
Mutable, non-thread-safe filter-limit configuration.
The result of bounded SCIM filter parsing.
Invalid syntax or a configured bound was exceeded; no partial tree is released.
An immutable filter.
An immutable declaration of supported filter shapes.
Mutable, non-thread-safe policy configuration.
A SCIM comparison literal: JSON string, number, boolean or null.
A JSON boolean literal.
JSON null, with no nullable payload.
A bounded exact decimal literal.
A well-formed UTF-16 string literal.
Visits each closed SCIM filter node kind on Java 17.
Intentional typed provisioning view; diagnostics are redacted.
Closed SCIM operation outcome with redacted diagnostics.
Rejected outcome.
Satisfied outcome.
Closed SCIM operation outcome with redacted diagnostics.
NotModified outcome.
Proceed outcome.
Rejected outcome.
Immutable SCIM operation budgets.
Mutable complete budget configuration; null restores each default.
Application-authored page framing for one approved query; storage and count accuracy are app-owned.
Mutable complete page configuration.
SCIM filter logical operators, in increasing precedence order OR, AND, NOT.
Ordered, ID-only Group membership instructions and the remaining resource operations.
Ordered instruction kinds; compare member IDs exactly, regardless of text collation.
One executable membership instruction at its original zero-based operation position.
Conservative membership reduction, full-evaluation fallback, or a fixed rejection.
Ordered ID instructions; success does not establish modification or authorization.
A fixed error without partial executable instructions.
Valid operations whose semantics cannot be represented as the conservative ID-only instructions.
SCIM write permissions attached to an attribute.
Fixed redacted events for SCIM operations.
Fixed public processing operation kinds, including separately sequenced PATCH operations.
Fixed direct-result classifications, without data or exception payloads.
Immutable advertised pagination capabilities.
Mutable, non-thread-safe pagination configuration; null restores the stated default.
SCIM PaginationMethod values.
A complete PATCH outcome with fixed rejection diagnostics and no partial success.
A fixed rejection with no partial payload.
The complete accepted payload.
A schema-bound operation created only by the PATCH parser.
A supported ordered SCIM PATCH operation.
A complete PATCH outcome with fixed rejection diagnostics and no partial success.
A fixed rejection with no partial payload.
The complete accepted payload.
An immutable ordered, schema-bound PATCH request.
An atomic candidate published only after every PATCH operation and final schema check succeeds.
Immutable engine-created query bound to its originating provider's schema and semantic registration.
Closed SCIM operation outcome with redacted diagnostics.
Rejected outcome.
Succeeded outcome.
Immutable schema-normalized application data.
Trusted document construction; invalid data is a programming error.
Trusted copying; null restores the source document.
A bounded create or replacement candidate; success is not authorization or persistence.
A fixed rejection with no partial candidate.
A normalized candidate and the canonical paths actually supplied by the accepted request.
Immutable application-resource registration.
Mutable, non-thread-safe complete resource-type configuration.
Trusted resource construction exceeded its configured processing work budget.
A fully bounded HTTP response prepared by a service provider.
Closed SCIM operation outcome with redacted diagnostics.
Prepared outcome.
Rejected outcome.
SCIM response visibility attached to an attribute.
Immutable SCIM schema registration.
Mutable, non-thread-safe schema configuration.
Immutable registration of a required or optional application-resource schema extension.
Immutable framework-neutral SCIM schema, request and response primitives.
Mutable complete provider configuration; null restores each documented default.
Mutable provider copy.
Immutable SCIM capability advertisement.
Mutable, non-thread-safe capability configuration; null restores the stated default.
SCIM SortOrder values.
Application-owned attribute-aware matching; deterministic, bounded and non-I/O.
Provider-constructible match outcome, without arbitrary failure data.
A matching verdict.
Matching is unsupported.
Advertised SCIM uniqueness responsibility, enforced by the application.
Intentional typed provisioning view; diagnostics are redacted.
A secret key for
StateSealer, 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 a
StateSealer.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.
A fixed set of verification keys, which never changes and is never fetched.
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.
Audience-checked RFC7662 JSON introspection using the supplied OAuth client settings.
Configures required audiences and optional introspection policy; OAuth settings are inherited.
Scope, resource and additional form options for one token request.
Mutable builder for one token request.
One token-endpoint success.
RFC 7009 revocation token-type hint.
Method provenance for a successful second-factor operation.
Standalone TOTP enrollment, once-only verification and recovery codes.
Caller-thread configuration builder.
A persisted pending enrollment whose secret is released only after a confirmed write.
Application-approved cancellation of an exact browser-bound pending enrollment.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
Infrastructure or recovery admission was unavailable; no success is established.
Application-approved account and display information for initial or replacement enrollment.
One caller-thread enrollment builder.
Pending enrollment preparation; provisioning material appears only after a confirmed commit.
A write may have occurred; reconcile management state and never infer authentication success.
Provisioning material whose pending record was definitely committed.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The durable shared account admission limit prevented this attempt.
Infrastructure or recovery admission was unavailable; no success is established.
Enrollment confirmation and atomic activation of a factor and recovery batch.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
The durable shared account admission limit prevented this attempt.
Infrastructure or recovery admission was unavailable; no success is established.
An active factor generation; this value contains no TOTP secret.
Atomic factor removal that retains permanent account and namespace fences.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
Infrastructure or recovery admission was unavailable; no success is established.
Explicit namespace initialization under provisioning admission.
The current namespace was already validly initialized.
A write may have occurred; reconcile management state and never infer authentication success.
The new namespace record and activation state were atomically initialized.
The requested transition is known committed, but normal output could not be admitted.
Infrastructure or recovery admission was unavailable; no success is established.
Non-secret pending-enrollment information for reconciling an uncertain management operation.
The exact immutable scope and sealing configuration requesting recovery admission.
The explicitly authorized recovery admission purpose.
Application-owned recovery admission barrier.
One caller-thread admission permit, with an idempotent prompt release.
Fixed, redacted application-visible reasons for rejected TOTP operations.
Non-secret account status at an authoritative read point; no authentication proof is conferred.
Authoritative non-secret status; absence never authorizes an application to downgrade MFA.
The account has no record in this epoch; application MFA requirements still apply.
An authoritative status read; this is not identity proof.
Infrastructure or recovery admission was unavailable; no success is established.
Application-owned, authoritative TOTP storage.
Immutable factual acknowledgement of an atomic TOTP write or predicate barrier.
Payload-free acknowledgement of an atomic TOTP write.
One explicit authoritative observation; omission never represents absence.
Confirmed absence at the authoritative snapshot point.
A versioned permanent sealed record.
Canonical, namespace- and recovery-epoch-bound address of permanent TOTP state.
Permanent record kinds.
Authoritative read outcome.
Complete observations at one authoritative snapshot point.
The requested recovery epoch is no longer authoritative.
An authoritative read could not be confirmed.
Opaque permanent record with an authenticated address and non-reused version.
Maintenance resealing of an exact authenticated durable record without changing semantic state.
The requested record was authoritatively absent in this recovery epoch.
The authenticated record already uses the configured active sealing key and current format.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
The authenticated record was resealed and the replacement definitely committed.
Infrastructure or recovery admission was unavailable; no success is established.
Complete immutable authoritative observations within exactly one namespace and recovery epoch.
An atomic comparison of every observed version and absence followed by all mutations or none.
An insertion or replacement of one permanent record.
Permanent insertion or replacement; deletion is deliberately unavailable.
Distinguishes one-time initialization from updates that cannot recreate the namespace.
Fixed operational reasons without account or secret data.
Library-created proof of a committed fresh TOTP acceptance; application login completion remains separate.
TOTP verification; only Succeeded carries a committed one-time acceptance.
A write may have occurred; reconcile management state and never infer authentication success.
The requested transition is known committed, but normal output could not be admitted.
Fixed input, policy or generation rejection; no proof is released.
The requested transition was definitely committed under current admission.
The durable shared account admission limit prevented this attempt.
Infrastructure or recovery admission was unavailable; no success is established.
Thrown when a token uses a JOSE feature that Revetsec does not support: encryption, the JSON serialization, a
critical header parameter, an unencoded or compressed payload, or a nested token.
Access-token proof released only after all configured profile checks.
App-authorized account fence transition that stops future passkey acceptance.
The fence is confirmed permanently disabled for this namespace/RP/account handle.
A write may have occurred; reconcile its actual effect through authorized fresh operations
before resuming dependent application actions.
The requested transition committed, but normal output could not be admitted.
Storage, recovery admission or a concurrent change prevented a confirmed result.
Engine-created proof of a committed, stored-key WebAuthn authentication.
The two authentication ceremonies.
Library-created sign-in or reauthentication preparation outcome.
A write may have occurred; reconcile before retry.
A committed, single-use browser request.
The requested transition committed, but normal output could not be admitted.
The approved account was not admitted for reauthentication.
Storage or admission was unavailable.
Library-created authentication completion; only Succeeded carries a verified identity.
A write may have occurred; reconcile before retry.
The requested transition committed, but normal output could not be admitted.
Fixed validation or policy rejection without an identity.
Confirmed stored-key authentication.
Storage or admission was unavailable.
Library-prepared browser options and opaque single-use ceremony handle.
App-authorized, authoritative credential listing result.
The account's active credential IDs at the authoritative read point.
The authoritative listing could not be established.
App-authorized credential removal; the app supplies session, CSRF and policy checks.
No active credential with this ID belongs to the approved account.
A write may have occurred; reconcile authoritative state before another action.
The requested transition committed, but normal output could not be admitted.
The credential was atomically revoked and removed from the active index.
Storage, recovery admission or a concurrent change prevented a confirmed result.
Checked account-pinned, action-bound WebAuthn reauthentication after admitted commitment.
Library-created reauthentication completion; only Succeeded carries a verified identity.
A write may have occurred; reconcile before retry.
The requested transition committed, but normal output could not be admitted.
Fixed validation or policy rejection without an identity.
Confirmed stored-key reauthentication.
Storage or admission was unavailable.
Application-owned admission barrier for authoritative WebAuthn operations.
One caller-thread permit.
Engine-created proof of a committed credential enrollment for an app-approved account.
Application-approved account information used only to prepare credential enrollment.
One caller-thread builder.
Library-created enrollment preparation outcome.
A write may have occurred; reconcile before retry.
A committed, single-use browser request.
The requested transition committed, but normal output could not be admitted.
Enrollment policy did not admit the approved account.
Storage or admission was unavailable.
Library-created enrollment completion; only Succeeded carries a verified registration.
A write may have occurred; reconcile before retry.
The requested transition committed, but normal output could not be admitted.
Fixed validation or policy rejection without an identity.
Confirmed enrollment of a new credential.
Storage or admission was unavailable.
Fixed, redacted reasons; no claimed account or browser detail is included.
Immutable WebAuthn relying party for discoverable, user-verified passkeys and security keys.
One caller-thread trusted configuration builder.
Bounded parser, ceremony and store-operation settings for a WebAuthn relying party.
One caller-thread settings builder.
Application-owned authoritative WebAuthn storage.
Immutable factual acknowledgement of an atomic WebAuthn write or predicate barrier.
Outcome of one atomic WebAuthn store write.
An explicit authoritative observation: a versioned sealed record or confirmed absence.
Confirmed absence, never an omitted read result.
A record and its opaque, non-reused compare-and-commit version.
Typed, namespace-bound authoritative address.
The five authoritative record kinds.
One authoritative read result.
A complete versioned snapshot.
The requested state incarnation is incompatible with current admission.
No authoritative read was available.
Complete immutable authoritative read set, including explicit absences.
One immutable atomic compare-and-commit request.
A typed insertion, replacement or deletion of a key from the read set.
The three atomic write operations.