Interface WebAuthnStore

All Known Implementing Classes:
InMemoryWebAuthnStore

@ThreadSafe @CheckReturnValue public interface WebAuthnStore
Application-owned authoritative WebAuthn storage. Shared implementations must coordinate all nodes, return a complete versioned snapshot, and atomically compare every predicate before applying all mutations. A confirmed commit must be durable for restart and cross-node continuity; InMemoryWebAuthnStore is an explicitly selected, volatile single-process option only. Data and admitted time must be one coherent observation. Timed writes compare the current authority, recovery and clock tuple, every predicate, and fresh time after all waits. Ordinary reads, barriers and no-effect refusals perform no hidden reclamation or quota update. A successful mutating commit may atomically reclaim expired ceremonies outside its predicate set using the same fresh healthy admitted time and their store-visible expiry hints; application stores must provide this bounded reclamation behavior or equivalent admitted maintenance. Permanent credentials, ownership tombstones, indexes, fences and stable namespace roots are never evicted to make room. A lost acknowledgement after a possible write is UNKNOWN, never CONFLICT or UNAVAILABLE. Implementations honor the remaining positive caller-thread budget and preserve interrupt status. Revetsec cannot preempt blocked application code or provide durability through this interface alone.
Since:
1.0.0
  • Method Details

    • read

      Reads every requested key at one authoritative snapshot point. A missing key is represented by an explicit WebAuthnStoreEntry.Absent entry. Admission retirement is Fenced; a provider failure is Unavailable, never fabricated absence.
      Parameters:
      keys - the complete bounded read set
      remainingBudget - the remaining positive operation budget
      Returns:
      a coherent complete snapshot, fenced result or unavailable result
      Since:
      1.0.0
    • compareAndCommit

      Compares all snapshot versions and absences at one linearization point and applies all changes or none. Fresh healthy authority time must satisfy the original inclusive floor and exclusive expiry after all waits and before mutations. An empty mutation set is a timed predicate barrier. A known late commit stays COMMITTED with timing; an uncertain mutation is never safe to retry.
      Parameters:
      write - the complete predicate and mutation set
      remainingBudget - the remaining positive operation budget
      Returns:
      the actual commit outcome
      Since:
      1.0.0