[Feature]: Desktop app: passkeys

Ouverte
#95 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
graphql, typescript

Piste de recherche

Read the #80 epic and #83 first, then inspect the desktop app’s sign-in and Settings → Account flows and the existing GraphQL mutations. The issue leaves the CTAP2 crate and authenticator implementation to be selected and audited; map that work before estimating the implementation. Done means registering, signing in with, and deleting a hardware key, with keys working between web and desktop.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement

[!NOTE]
This issue was written by Claude (Claude Opus 5.5) from a planning session with @PhrolovaMoe. Part of #80, builds on #83. Read the epic first.

Area

Desktop app

Problem

The web signs in with passkeys, but a native Linux app has no browser WebAuthn. The server only accepts security keys (danger_set_user_presence_only_security_keys), so the desktop must talk to hardware keys itself.

Proposed solution
  • CTAP2 over USB HID, behind an Authenticator trait (Windows has webauthn.dll and macOS has AuthenticationServices for later). Pick the crate (ctap-hid-fido2, Mozilla's authenticator, or a small own implementation) by which passes the audit with fewer crates and supports CTAP2 PIN + user presence. NFC/BLE are out of scope.
  • Flows, with the existing GraphQL mutations:
    • sign in: startPasskeySignIn(username, profile) → finishPasskeySignIn(challenge, credential);
    • register: startPasskeyRegistration(name) → finishPasskeyRegistration(challenge, credential);
    • list and delete: passkeys, deletePasskey(id).
  • The server builds its relying party from the request's Origin header (webauthn_for in src/auth/passkeys.rs). The app sends Origin: <server origin> on these requests and builds clientDataJSON with that origin, as a browser on the server's page would. So passkeys work exactly where they work on web: https:// servers and http://localhost. Show the web's message otherwise. Confirm no server change is needed; if one is, make it minimal and keep web behaviour identical.
  • UI as on web: the passkey button on the sign-in screen (when the server's sign-in style allows it), "touch your key" and PIN prompts, the passkey list in Settings → Account.
  • Linux needs read/write access to the key's hidraw device. Most distros grant it through udev's FIDO rules. When access is denied, say so with a hint about the udev rule.
Done when

With David's hardware key: register a key from the app, sign in with it on a fresh server entry, delete it. A key registered on web signs in from the app and the other way round.

Langage dominant
TypeScript
Étoiles
4
Forks
1
Merge moyen
4 h 49 min
PR mergées (30 j)
5

Préparer son environnement

  • Fournit un Dockerfile ou un fichier Docker Compose
  • Aucun modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de tinystream-dev/tinystream

Toutes les issues de tinystream-dev/tinystream

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.