[Feature]: Desktop app: passkeys

Abierto
#95 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
graphql, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
4
Forks
1
Merge medio
4 h 49 min
PR fusionados (30 d)
5

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tinystream-dev/tinystream

Todos los issues de tinystream-dev/tinystream

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.