Epic: native and desktop apps on the OpenID Provider
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
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)
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- Avg merge
- 11h 40m
- Merged PRs (30d)
- 104
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fells-code/seamless-auth-api
-
easy P2 v0.23
Difficulty 4/5 Over a week Newbie friendliness 8/100
fells-code/seamless-auth-api#561 ·
Maintainers usually reply within 1 day
-
epic P1 security v0.23
Difficulty 5/5 Over a week Newbie friendliness 8/100
fells-code/seamless-auth-api#558 ·
Maintainers usually reply within 1 day
-
P1 security v0.23
Difficulty 3/5 Half a day Newbie friendliness 55/100
fells-code/seamless-auth-api#553 ·
Maintainers usually reply within 1 day
-
P2 secure v2.1
Difficulty 5/5 Over a week Newbie friendliness 25/100
fells-code/seamless-auth-api#512 ·
Maintainers usually reply within 1 day
-
P3 secure v1.0
Difficulty 3/5 1-2 days Newbie friendliness 55/100
fells-code/seamless-auth-api#439 ·
Maintainers usually reply within 1 day
All issues in fells-code/seamless-auth-api
Similar issues
-
desktop v3 windows
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
esengine/DeepSeek-Reasonix#15016 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
readest/readest#7413 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: medium size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
eliasstravik/herdr-projects#788 ·