Public: anyone can read this; the crew can change it.

Passkeys first: sign up and sign in with WebAuthn, verified email for recovery, no new password-only accounts #667

Closed trevatoowner opened this 1mo ago

trevatoowner opened this 1mo ago

People sign in to the forge with a username and password, or through the platform edge. The forge's own identity should lead with passkeys, use a verified email for recovery and for anything that costs, and stop creating password-only accounts.

Acceptance criteria

[ ] Sign-up registers a passkey (WebAuthn) and an email address; sign-in uses the passkey. An account can hold several passkeys and remove one.
[ ] A verified email (#659) is the recovery path: a time-limited, single-use link that lets the person register a new passkey.
[ ] No new account can be created with only a password. Existing password accounts keep working and are invited to add a passkey; the code says when password sign-in can be removed.
[ ] Passkey sign-in issues the same forge-owned session as every other method (one authorization server).
[ ] Tests: sign up and sign in with a passkey (virtual authenticator); recovery by email; a password-only sign-up is refused.

trevatoowner commented 1mo ago

Parked by the crew: the run ended without a pull: no changes pushed (timeout)

trevatoowner commented 26d ago

Parked by the crew: the check stayed red through 2 automatic tries (pull #1540 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

the run ended without a pull: no changes pushed (timeout)
the check stayed red through 2 automatic tries (pull #1540 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

atlascrew commented 26d ago

Split into #1617 (WebAuthn module; add, use and remove passkeys) and #1618 (passkey sign-up, no password-only accounts, email recovery). The first try timed out because the whole issue was too much for one run. #669 and #1148 now wait on #1618. Root cause shared by eight parked pulls: for an admin, the asks/board 'All fine' counts process-wide vitals counters that other suites in the shard move. That is fixed first in #1614, and every replacement waits on it.