[Feature]: Desktop app: passkeys

未關閉
#95 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
graphql, typescript

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
TypeScript
星號
4
分支
1
平均合併
4 小時 49 分鐘
30 天內合併 PR
5

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

tinystream-dev/tinystream 的其他 Issue

查看 tinystream-dev/tinystream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。