Package com.revetsec.totp
@NullMarked
package com.revetsec.totp
Time-based one-time passwords and single-use recovery codes with application-owned
authoritative storage and recovery admission. Successful verification and recovery-code
consumption are distinct method proofs; the application owns account authorization,
login completion, session policy and a recovery epoch outside restored storage.
Provisioning URIs, manual-entry keys and newly issued recovery codes contain secrets.
- Since:
- 1.0.0
-
ClassDescriptionExplicit bounded, volatile, single-process TOTP demonstration store.Caller-thread configuration for explicit volatile storage.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.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.