Linus Rath 3f01e94319 fix: key synced settings on the account a bearer token belongs to ...

A Bearer login may claim a bare local part, which is accepted when the
server's `Session.username` has the same local part (TOTP users who
type `john` log in this way). Settings were keyed on that claim, so on a
multi-domain server `john@b.example` could claim `john` and read and
overwrite the synced settings of the `john@a.example` who signs in as
`john` with a password.

`resolveJmapIdentity` now returns the canonical account name for a bare
Bearer claim, the context cookie carries it as `accountName`, and the
settings route keys on it. Basic logins and fully-qualified claims keep
their existing key.

2026-09-26 14:59:55 +02:00

..

auth-context.ts

fix: key synced settings on the account a bearer token belongs to

2026-09-26 14:59:55 +02:00

credentials.ts

fix: pin resolved IP for stored custom JMAP endpoints and branding URLs

2026-08-26 23:02:19 +02:00

jmap-api.ts

fix: pin resolved IP for stored custom JMAP endpoints and branding URLs

2026-08-26 23:02:19 +02:00

jmap-passthrough.ts

feat: add Bulwark Lite static export build

2026-09-17 23:54:33 +02:00

principal.ts

fix: let non-admin users see their name and change a TOTP password

2026-09-22 20:28:01 +02:00

server-fetch.ts

fix: pin resolved IP for stored custom JMAP endpoints and branding URLs

2026-08-26 23:02:19 +02:00