Phase 1: accounts and sessions
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s

Implements PLAN.md Phase 1. A client can now register, log in, manage its
devices and set its profile; an operator can create accounts and flip the
runtime switches. There are still no rooms and no real /sync.

userapi: accounts, argon2id passwords in PHC format, devices, access and
refresh tokens stored as SHA-256 hashes, account data and the admin flag.
Its storage interface is storage.UserStore, implemented once in sqlstore
with `?` placeholders; the postgres driver supplies a rebind function and
unique-violation recognition rather than keeping a second copy of thirty
statements. Timestamps in these tables are int64 milliseconds, the unit the
Client-Server API uses on the wire.

Client-Server API: register (user-interactive auth with m.login.dummy and
optional registration tokens), register/available, token validity, login
with m.login.password, logout, logout/all, refresh, account/whoami,
capabilities, devices/* with password-gated deletion, profile/*, global and
per-room account data.

GET /sync is a deliberate placeholder: it answers a valid token with an
empty but well-formed response and refuses a revoked one. Phase 1 has no
rooms, so that is the whole truth, and it is what makes session revocation
observable. Phase 4 replaces it with the syncapi.

Auth middleware resolves a bearer token (header or the legacy query
parameter) to a device and user, answering an expired token with the soft
logout the spec asks for. Rate limiting is a token bucket per endpoint class
keyed on the client address, returning M_LIMIT_EXCEEDED with retry_after_ms.

adminapi v1 under /_warp/admin/v1: admin-only auth via a normal Matrix
token, GET/PUT /federation and /registration driving internal/settings and
reporting a config-pinned switch as a 409, GET/POST /users, GET /stats.

warp create-account [--admin] creates the first account straight in the
database, so a new install with registration off has a way in.

Complement is wired up for the federation=off profile: an image meeting its
contract, an entrypoint that configures Warp entirely from WARP_*
variables, and a runner that builds, clones and executes the target set
(TestRegistration, TestLogin, TestDeviceManagement). It has not been run
yet -- there is no container runtime on the development machine -- so the
three tests' assertions were read from the Complement sources and pinned as
httptest tests instead, and CI gained a job that runs the real thing.

Also fixes a .gitignore bug from Phase 0: the unanchored `warp` pattern,
meant for the built binary, also matched the directory server/cmd/warp and
silently excluded the entire command package from the repository. The
binary patterns are now anchored to the repository root, and cmd/warp is
committed for the first time.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tajniak81andClaude Opus 5 committed 2026-10-15 18:18:37 +02:00
1 parent b4fb60a8ab
commit 6004bb01de
68 files changed
+9729 -66

No files matched your search

+50
View File
@@ -97,6 +97,21 @@ jobs:
WARP_TEST_POSTGRES_DSN: postgres://warp:warp@localhost:5432/warp_test?sslmode=disable
run: go test -count=1 ./internal/storage/...
complement:
name: Complement (federation off)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: ${{ env.GO_VERSION }}
# Complement is a separate Go module with its own dependencies; the
# runner script clones it into .complement/.
- name: Run the Complement subset for the phases that are done
run: bash server/test/complement/run.sh
lint:
name: golangci-lint
runs-on: ubuntu-latest
@@ -154,6 +169,41 @@ jobs:
status="$(curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8008/.well-known/matrix/server)"
test "$status" = "404"
# Registration is off in a fresh install, so the first account is
# made from the command line. Everything from here on is the
# Phase 1 surface, through the real binary.
./bin/warp create-account --username ci-admin --password hunter2hunter2 --admin
token="$(curl -fsS http://127.0.0.1:8008/_matrix/client/v3/login -d '{
"type": "m.login.password",
"identifier": {"type": "m.id.user", "user": "ci-admin"},
"password": "hunter2hunter2"
}' | sed -n 's/.*"access_token":"\([^"]*\)".*/\1/p')"
test -n "$token"
curl -fsS http://127.0.0.1:8008/_matrix/client/v3/account/whoami \
-H "Authorization: Bearer $token" | grep -q '@ci-admin:ci.example'
curl -fsS http://127.0.0.1:8008/_matrix/client/v3/capabilities \
-H "Authorization: Bearer $token" | grep -q 'm.room_versions'
curl -fsS http://127.0.0.1:8008/_warp/admin/v1/stats \
-H "Authorization: Bearer $token" | grep -q '"admins":1'
# An unauthenticated request must be refused, not served.
status="$(curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:8008/_warp/admin/v1/stats)"
test "$status" = "401"
# Registration is refused while the switch is off, and accepted
# once the admin API flips it — with no restart.
status="$(curl -s -o /dev/null -w '%{http_code}' -X POST \
http://127.0.0.1:8008/_matrix/client/v3/register -d '{}')"
test "$status" = "403"
curl -fsS -X PUT http://127.0.0.1:8008/_warp/admin/v1/registration \
-H "Authorization: Bearer $token" -d '{"enabled":true}' | grep -q '"enabled":true'
status="$(curl -s -o /dev/null -w '%{http_code}' -X POST \
http://127.0.0.1:8008/_matrix/client/v3/register -d '{}')"
test "$status" = "401"
# Graceful shutdown: SIGTERM must stop the process cleanly.
kill -TERM "$server_pid"
wait "$server_pid"