Install the current suite: inbuxa-webmail, and the server's token-only sign-in #6

Merged
jcoffey-dev merged 1 commits from pins/inbuxa-webmail into main 2026-10-05 05:57:09 +00:00
Owner

Moves the installer to the current suite and the webmail's new name: server 2026.9.30.2, console 2026.9.30, webmail inbuxa-webmail:2026.10.5-g17a8093 (was inbuxa-server:2026.9.23, inbuxa-admin:2026.9.21.2, ihasmail-inbuxa:2026.9.22-gc2f13d6). The webmail couldn't move alone: since 2026.9.26 it needs the server's renamed registry capability, which 2026.9.23 doesn't have.

The newer server needed three changes here:

  1. Capability name. The JMAP client sends urn:inbuxa:jmap:registry instead of urn:stalwart:jmap, which the server now refuses.

  2. First boot under C-23. A configured server refuses HTTP Basic on /jmap, and in bootstrap mode only x:Bootstrap answers, so the administrator can't get a token over JMAP. After bootstrap:

    • the server comes up once with INBUXA_HTTP_BASIC_AUTH=all, set from a one-step override file, the way the bootstrap credential already is;
    • the administrator uses its password to create its own API key, which expires in one hour;
    • the server is recreated without the override, so C-23 applies again before anything else runs.

    The key does the rest of the setup as a Bearer token and is destroyed at the end. If setup stops early, the key lapses on its own.

  3. --local webmail sign-in. The local shape used to sign in with a password, which the webmail would now have to pass on as Basic. It now uses the server's page as the first-party OAuth client, like a public install. The server gets INBUXA_PUBLIC_URL set to its loopback address, so its sign-in page and OAuth metadata point somewhere a browser can reach. PUSH_URL is still public-only: local tabs use the relay.

Tests, on the debian13 lab:

  • install-local: 26/26. It now signs in end to end the way a browser does: from the webmail, to the server's /api/auth, then back with the code. It also checks the override is gone and the administrator's password is refused on /jmap.
  • install-public: 20/20. One earlier run had a single connection miss on the sign-in page fetch, and the re-run passed.
  • topology: 28/28.
  • status-export: 16/16.
  • Unit tests: pass, with new ones for the API key and the Bearer header.

Not in this PR: #5. The server's data lands in anonymous volumes, and fixing that needs a migration.

Moves the installer to the current suite and the webmail's new name: server `2026.9.30.2`, console `2026.9.30`, webmail `inbuxa-webmail:2026.10.5-g17a8093` (was `inbuxa-server:2026.9.23`, `inbuxa-admin:2026.9.21.2`, `ihasmail-inbuxa:2026.9.22-gc2f13d6`). The webmail couldn't move alone: since 2026.9.26 it needs the server's renamed registry capability, which 2026.9.23 doesn't have. The newer server needed three changes here: 1. **Capability name.** The JMAP client sends `urn:inbuxa:jmap:registry` instead of `urn:stalwart:jmap`, which the server now refuses. 2. **First boot under C-23.** A configured server refuses HTTP Basic on `/jmap`, and in bootstrap mode only `x:Bootstrap` answers, so the administrator can't get a token over JMAP. After bootstrap: - the server comes up once with `INBUXA_HTTP_BASIC_AUTH=all`, set from a one-step override file, the way the bootstrap credential already is; - the administrator uses its password to create its own API key, which expires in one hour; - the server is recreated without the override, so C-23 applies again before anything else runs. The key does the rest of the setup as a Bearer token and is destroyed at the end. If setup stops early, the key lapses on its own. 3. **`--local` webmail sign-in.** The local shape used to sign in with a password, which the webmail would now have to pass on as Basic. It now uses the server's page as the first-party OAuth client, like a public install. The server gets `INBUXA_PUBLIC_URL` set to its loopback address, so its sign-in page and OAuth metadata point somewhere a browser can reach. `PUSH_URL` is still public-only: local tabs use the relay. **Tests**, on the debian13 lab: - **install-local:** 26/26. It now signs in end to end the way a browser does: from the webmail, to the server's `/api/auth`, then back with the code. It also checks the override is gone and the administrator's password is refused on `/jmap`. - **install-public:** 20/20. One earlier run had a single connection miss on the sign-in page fetch, and the re-run passed. - **topology:** 28/28. - **status-export:** 16/16. - **Unit tests:** pass, with new ones for the API key and the Bearer header. Not in this PR: #5. The server's data lands in anonymous volumes, and fixing that needs a migration.
jcoffey-dev added 1 commit 2026-10-05 05:54:51 +00:00
Pins server 2026.9.30.2, console 2026.9.30 and webmail
inbuxa-webmail:2026.10.5-g17a8093, the repository's new name. Those
releases need three changes here:

- The JMAP client asks for urn:inbuxa:jmap:registry, the registry
  capability's name since the server renamed it.
- Configured servers refuse HTTP Basic on /jmap (contract C-23), and in
  bootstrap mode nothing but x:Bootstrap answers. So after bootstrap the
  server comes up once with INBUXA_HTTP_BASIC_AUTH=all, from a one-step
  override file, long enough for the administrator to give itself an API
  key; it is then recreated without the override. The key, as a Bearer
  token, does the rest of the setup, is destroyed at the end and expires
  within the hour regardless.
- --local signs in to the webmail through the server's page as well, as
  the first-party OAuth client: a password sign-in would have nothing to
  pass the password on with. The server is told its loopback address as
  INBUXA_PUBLIC_URL, so its sign-in page and OAuth metadata point where a
  browser can reach them.

install-local now signs in end to end the way a browser does, and checks
that the Basic override did not outlive the setup.
jcoffey-dev merged commit 2fce971081 into main 2026-10-05 05:57:09 +00:00
jcoffey-dev deleted branch pins/inbuxa-webmail 2026-10-05 05:57:10 +00:00
Sign in to join this conversation.