Files
zeekay 38a09776dc device: a stranger's request is pinned, bounded and shown for what it is
Red's findings H1, M2-M5 and L1-L4 on the device grant:

- The scope a device carries is the application's to give: declared scopes, else the
  standard OIDC set; `openid admin kms:write *` is `openid`; past 2048 bytes is refused.
- The row records where it was started (edge-delivered address and country, never a
  client-written forwarded hop) and device/info shows it with the pinned scope.
- On the brand's site the code rides the URL fragment, so no server, log, Referer or CDN
  analytics sees it. TTL is ten minutes.
- The start is budgeted per client and per address; expired unapproved rows are swept; a
  pending poll under four seconds after the last is slow_down.
- Approve, refuse and the poll's burn decide under a row lock (store.WithToken), so one
  outcome stands and a request is minted once.
- Wrong codes are counted per account; past ten in fifteen minutes every answer is the one
  refusal, which now also covers a live code that is not the caller's tenant.
- A SuperAdmin crosses tenants only for the platform's own applications.
- signinUrl is validated on create and update, and authorize follows it only to an origin
  IAM signs people in at: the issuer was an open redirector for any tenant's application.

Claude-Session: https://claude.ai/code/session_015XYKLnjAuGqkk4ssA1Jusy
2026-11-08 15:50:43 -08:00
..
2026-09-09 00:03:43 -07:00