octoturge b4948076a0 Trade the gateway token for an edge JWT on every connection ...

The proxy put its configured gateway_token straight into the upgrade's
Authorization header, but the backend only accepts a one-hour edge JWT
(scope "edge") there, minted by POST /auth/edge-token from the farm's edge
proxy token. Nothing in the proxy ever made that call, so a gateway
configured with the token the console hands out could not connect at all,
and one given a hand-minted JWT (which is what every test did) would have
been locked out an hour later on its first reconnect.

Each connection attempt now starts by trading gateway_token for a fresh JWT,
at an address derived from the socket URL so there is one to configure. A
401 is reported as what it means (token rotated or wrong), since retrying
will not fix it. Config's Debug no longer prints the token.

tests/uplink_late_result.rs now plays the cloud's exchange endpoint and
asserts the socket opens with the minted JWT, not the configured token.
.env.example and continuum.example.toml say what the token is.

2026-10-29 15:10:27 +00:00

..

fixtures

Derive the AMS mapping from the project, and blink on completion

2026-10-15 21:27:24 +00:00

discovery_to_fleet.rs

Report discovered printers to the cloud, off by default

2026-10-19 08:21:30 +00:00

push_status_parsing.rs

Model vt_tray and the stage fields, and use them

2026-10-15 21:37:20 +00:00

uplink_late_result.rs

Trade the gateway token for an edge JWT on every connection

2026-10-29 15:10:27 +00:00

uplink_protocol.rs

Send the edge token on the upgrade, not in the hello

2026-10-17 14:00:05 +00:00