Epic: native and desktop apps on the OpenID Provider

未关闭
#551 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
5/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

This is an epic tracking child issues, not a single task, so start from the linked sub-issues and ADR 0002 at docs/adr/0002-native-and-desktop-apps.md (#550). The already-shipped items #510 and #508 are done and only need checking against the design. There is no concrete change to make here, and a newcomer should pick one child issue with a named file or test instead.

由索引模型根据 Issue 内容生成。

描述

epic P2 v0.23

Goal

Any desktop app with its own backend API can run on Seamless Auth from registry configuration alone: sign-in through the system browser, a backend that verifies access tokens and requires a recent phishing-resistant sign-in per route, and account notices from that backend to the app's users.

Design

ADR 0002 (docs/adr/0002-native-and-desktop-apps.md, #550). The same design covers SPAs and mobile apps with a backend.

Scope

Admin-set client links and notices through them, step-up claims on JWT access tokens, a local development recipe for the edge, and a runnable desktop and backend example with its guide.

Children are linked as sub-issues. Two related issues stay under the v0.21 epic #387:

  • #510 step-up at the edge and in ID tokens (shipped in v0.21; its resource server half is seamless-auth-oidc-provider#34)
  • #508 native public clients with loopback redirects (shipped in v0.21)
主要语言
TypeScript
星标
2
派生
2
平均合并
11 小时 40 分钟
30 天内合并 PR
104

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fells-code/seamless-auth-api 的其他 Issue

查看 fells-code/seamless-auth-api 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。