mirror of
https://github.com/nestriness/nestri.git
synced 2026-09-19 17:25:19 +03:00
f25c9af545
The issuer kept everything behind one get/set/remove/scan interface, which is what a library that must run on any provider's cache can offer. Three of the things kept there could not actually be served by it. An authorization code must be redeemable once and a refresh token spendable once, and through get and set the check and the write are separate steps — so two requests arriving together both read an unspent record, and both mint a session. In the refresh case that also means the reuse which reveals a stolen token is never recorded, because recording it is the write that the second caller overwrites. Each now has a table and an interface of its own: redeeming is one `delete ... returning`, spending is one `update ... where time_used is null returning *`, so exactly one caller is ever told it went first. This is the same argument the device grant already made, applied to the two records that had it too. Signing keys move for a different reason. Nothing races for them; they are the one record whose loss ends every session at once, and a cache is a place things may be evicted from. They are retired by setting a column rather than deleted, so the tokens they signed stay verifiable until they expire. Both credential tables store a hash and never the credential, as the device grant does. An authorization code travels in a query string and so passes through history, referrer headers and any log along the redirect; a refresh token resumes a session outright. What is left in the generic store is the rate-limit counters — written far more often than read, meaningless within the hour, and allowed to be approximate, since a lost increment costs one guess out of ten. Those move to Postgres too, so the only key-value binding this deploys with is gone and the control plane's state is one database. That was the point: nothing here now depends on a primitive a self-hoster cannot run. The generic scan also gained the separator on its prefix, so scanning `a` cannot return what is under `ab` — subjects and email addresses are both prefixes of longer subjects and email addresses. Deploying this signs everyone out. The signing keys and refresh tokens are in a store that is being left behind, so the issuer starts with a fresh key set and every existing token stops verifying.
43 lines
2.1 KiB
Markdown
43 lines
2.1 KiB
Markdown
# apps/auth
|
|
|
|
The authentication worker for Nestri — a Cloudflare Worker built on
|
|
[`@nestri/auth`](../../packages/auth/README.md) (OpenAuth-style issuer).
|
|
|
|
## What it does
|
|
|
|
Hosts the OAuth issuer and the sign-in UI:
|
|
|
|
- **Email code** — the only provider, on purpose. Verifying an email address is the one thing that
|
|
brings an account into existence, so an account is exactly as recoverable as its email. The
|
|
`success` callback finds or creates the `User` row, ensures a personal team exists, and issues a
|
|
JWT `user` subject containing `{ userID, linkedAccountID }`.
|
|
- **Device authorization grant** (RFC 8628) — for programs with no browser. A client starts a grant,
|
|
a person approves it in a browser, and the client collects tokens by polling. Connecting a Steam
|
|
account is not a sign-in and lives in `apps/api` instead, against a user who already exists.
|
|
|
|
## Key details
|
|
|
|
- **All issuer state is in Postgres.** There is no key-value binding. Signing keys, authorization
|
|
codes, refresh tokens and device grants each have a table, because each is either a record whose
|
|
loss ends every session (the keys) or one with a transition that must happen exactly once while
|
|
two callers are touching it — a code is redeemed once, a refresh token is spent once, a grant is
|
|
approved once. A store that reads and writes whole records cannot promise that. What is left in
|
|
the generic `auth_kv` table is the rate-limit counters, which are allowed to be approximate.
|
|
- Authorization codes, refresh tokens and device codes are stored as hashes. Each is a bearer
|
|
credential, so what is kept is enough to recognise one and not enough to present it.
|
|
- JWT subjects are defined in `@nestri/core/auth/subjects`.
|
|
- The API worker verifies tokens against this issuer through `AUTH_ISSUER_URL`.
|
|
|
|
## Structure
|
|
|
|
```text
|
|
src/index.ts # Worker entrypoint: issuer config, stores, success callback
|
|
src/email.ts # Verification code delivery
|
|
test/ # Worker tests
|
|
```
|
|
|
|
## Running
|
|
|
|
Deployed through Alchemy (`apps/auth` worker in `alchemy.run.ts` at the repo root). Its only
|
|
stateful binding is `HYPERDRIVE` (Postgres), alongside the mail settings.
|