mirror of
https://github.com/nestriness/nestri.git
synced 2026-09-19 09:15:19 +03:00
refactor(api)!: remove the shared operator secret, and let hosts sync their own
A single secret that turned any request into an operator was the only credential several routes accepted, and it had no caller left: the device pairing it existed for is on hold, and nothing in this tree or any client sent it. What remained was a key that bypassed authentication entirely, required to boot, and checked by nobody. Every route behind it had a better answer available: - Library and game sync move to host credentials. Both took a `userId` in the body, which meant one secret could write into anybody's library. A host now says which of its enrolled users a batch is for, and that claim is checked against the Steam sign-ins it actually holds — one box carries several people's accounts, so the pair is the unit. - Download-state reporting narrows to hosts alone, and the body that could name a different host is gone. Which host is reporting comes from its own credentials, and a body that still names one is refused rather than ignored. - Linking a Steam account is always for the caller. - Creating a game by hand is deleted; syncing already upserts the catalogue. - Reading the waitlist is deleted. Every address on it belongs to someone who has not agreed to anything, and answering it over HTTP made that list something a leaked key could drain. - The pairing-code routes are deleted with the flow they served. The domain module and its table stay, so returning to it is a route file rather than a migration. Nothing in the API now accepts a credential that stands for more than one caller: every request resolves to a specific user or a specific host, which is what lets a route say "the caller's own library" and mean it. BREAKING CHANGE: the `x-nestri-admin-token` header is no longer accepted and `ADMIN_SHARED_SECRET` is no longer read. `POST /games`, `GET /waitlist` and the `/pairing-code` routes are gone; `POST /games/sync` and `POST /library/sync` now require host credentials and take `userId` in the body; `POST /steam/link` no longer accepts `userId`; `POST /games/download-state` no longer accepts `hostId`.
This commit is contained in:
@@ -11,17 +11,17 @@ and returns `{ data: ... }`. All business logic lives in the core package.
|
||||
|
||||
Routes:
|
||||
|
||||
| Prefix | Purpose |
|
||||
| ----------------- | ------------------------------------------------------------- |
|
||||
| `/` | Health check |
|
||||
| `/user` | Current user profile, fingerprints, linked accounts |
|
||||
| `/steam` | Link / sync / unlink a Steam account |
|
||||
| `/library` | Owned games with playtime |
|
||||
| `/games` | Game catalog |
|
||||
| `/pairing-code` | Device pairing codes |
|
||||
| `/machine` | Host machines |
|
||||
| `/access-token` | Short-lived access tokens |
|
||||
| `/doc` | Generated OpenAPI spec |
|
||||
| Prefix | Purpose |
|
||||
| --------------- | --------------------------------------------------- |
|
||||
| `/` | Health check |
|
||||
| `/user` | Current user profile, fingerprints, linked accounts |
|
||||
| `/steam` | Link / sync / unlink a Steam account |
|
||||
| `/library` | Owned games with playtime |
|
||||
| `/games` | Game catalog |
|
||||
| `/pairing-code` | Device pairing codes |
|
||||
| `/machine` | Host machines |
|
||||
| `/access-token` | Short-lived access tokens |
|
||||
| `/doc` | Generated OpenAPI spec |
|
||||
|
||||
## Structure
|
||||
|
||||
@@ -29,7 +29,7 @@ Routes:
|
||||
app/
|
||||
index.ts # The handler: middleware, routes, error handler, /doc
|
||||
server.ts # The same handler behind a listening socket
|
||||
middleware/auth.ts # Bearer JWT + admin shared-secret auth → Actor
|
||||
middleware/auth.ts # Bearer JWT, access token or host credentials → Actor
|
||||
routes/*.ts # Thin route namespaces (UserApi, SteamApi, ...)
|
||||
utils/ # ErrorResponses, Result(), validator wrapping
|
||||
wrangler.jsonc # Worker configuration, one environment per stage
|
||||
@@ -39,12 +39,11 @@ test/ # Route tests
|
||||
|
||||
## Key details
|
||||
|
||||
- Auth: `Authorization: Bearer <JWT>` verified against `@nestri/auth`; or the `x-nestri-admin-token` header
|
||||
carrying `ADMIN_SHARED_SECRET`, which bypasses JWT verification entirely and is required — it has no
|
||||
default anywhere. It is what authenticates the callers that have no user identity to present:
|
||||
`POST /pairing-code/claim` (a device being paired has no identity yet, which is the whole point),
|
||||
`POST /games`, `POST /games/sync`, `POST /library/sync`, `GET /waitlist`, `POST /steam/link` on behalf
|
||||
of another user, and `POST /games/download-state` when an operator is repairing state a box reported.
|
||||
- Auth: `Authorization: Bearer …`, carrying either a session token verified against `@nestri/auth`
|
||||
or a personal access token resolved from the database; or a registered host's own
|
||||
`x-nestri-machine-id` and `x-nestri-machine-secret`. There is no shared secret and no credential
|
||||
that stands for more than one caller, so every route resolves to a specific user or a specific
|
||||
host — which is what lets a route say "the caller's own library" and mean it.
|
||||
- Errors: centralized `VisibleError` → typed JSON responses.
|
||||
- Settings arrive as bindings or as environment variables, and two of them have one spelling of
|
||||
each: Postgres is `HYPERDRIVE` or `DATABASE_URL`, and the route to the issuer is an `AUTH`
|
||||
@@ -60,4 +59,4 @@ bun run serve # as a plain process, on $PORT (default 3000)
|
||||
```
|
||||
|
||||
Needs a Postgres database and a reachable issuer. Full list and deployment steps:
|
||||
[`docs/deploy.md`](../../docs/deploy.md).
|
||||
[`docs/deploy.md`](../../docs/deploy.md).
|
||||
|
||||
Reference in New Issue
Block a user