[Feature]: Desktop app: passkeys
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
- Área
- authentication, desktop
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
[!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
Authenticatortrait (Windows haswebauthn.dlland macOS has AuthenticationServices for later). Pick the crate (ctap-hid-fido2, Mozilla'sauthenticator, 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).
- sign in:
- The server builds its relying party from the request's
Originheader (webauthn_forinsrc/auth/passkeys.rs). The app sendsOrigin: <server origin>on these requests and buildsclientDataJSONwith that origin, as a browser on the server's page would. So passkeys work exactly where they work on web:https://servers andhttp://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
hidrawdevice. 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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de tinystream-dev/tinystream
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tinystream-dev/tinystream#132 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tinystream-dev/tinystream#131 ·
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
tinystream-dev/tinystream#129 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
tinystream-dev/tinystream#128 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tinystream-dev/tinystream#124 ·
Todos los issues de tinystream-dev/tinystream
Issues similares
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
sandbox-quantum/switch#2163 ·
Los mantenedores suelen responder en 1 día
-
automated issue report
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area/dashboard kind/bug QA/dev-automation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
bug pydanty:is-working
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
pydantic/pydantic-ai#13939 ·
Los mantenedores suelen responder en 1 día
-
self-host
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
funmusicplace/mirlo#2625 ·
Los mantenedores suelen responder en 1 día