Skip to content

M2-08 Passkey Support

Milestone: M2 — Platform and Client Admin SOW Reference: Not in the SOW — present only in the earlier v3 High-Level Requirements doc ("Passkey is desirable to be implemented also") Requirement Clarity: 🟡 Confirm whether this is still wanted; the SOW is silent on it Dev Status: ❌ Not started — Passkey entity exists as schema only, no enrollment/auth flow

Overview

WebAuthn/passkey login as an alternative or supplement to password + MFA. Marked "desirable" (not mandatory) in the original requirements doc, then dropped without comment in the SOW.

Backend Tasks

  • Get written confirmation from Curo on whether this is in or out of scope
  • If in scope: implement WebAuthn credential registration/verification, wiring up the existing Passkey entity (app/backend/src/users/entities/passkey.entity.ts)

Frontend Tasks

  • If in scope: add passkey registration UI and passkey-based login option

Dependencies

  • M2-07 MFA — related authentication-factor work, likely built together if in scope.

Acceptance Criteria

To be defined once scope is confirmed.

Existing Reference Material

Blockers & Risks

  • Blocking (low-cost to resolve): this is a single yes/no question to Curo, not an estimation problem — resolve early rather than let it linger as ambiguous scope.