Uses of Package
com.revetsec.totp
Packages that use com.revetsec.totp
Package
Description
Time-based one-time passwords and single-use recovery codes with application-owned
authoritative storage and recovery admission.
-
Classes in com.revetsec.totp used by com.revetsec.totpClassDescriptionExplicit 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 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.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.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.Enrollment confirmation and atomic activation of a factor and recovery batch.An active factor generation; this value contains no TOTP secret.Atomic factor removal that retains permanent account and namespace fences.Explicit namespace initialization under provisioning admission.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.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.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.