Skip to content

feat(broker): logins for the clients of the published MQTT port (#1964) - #1967

Open
groupsky wants to merge 4 commits into
masterfrom
feat/1964-mqtt-logins
Open

groupsky wants to merge 4 commits into
masterfrom
feat/1964-mqtt-logins

Conversation

@groupsky

@groupsky groupsky commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Refs #1964

What

  • Port 1883 stays anonymous, but is published only on routy's 127.0.0.1. Services on the docker networks use broker:1883 and do not change. Tools on routy itself keep working.
  • New login-only port 1885 for the server clients outside docker, with config/mosquitto/servers.acl and its own password file servers.passwd (from the deploy, never in git).
  • Port 1884 (car, routy: MQTT: a car-only user that may only publish and read the car's topics #1962) is unchanged.
  • Client list, users and setup: docs/mqtt-car-user.md.

Why this way

  • A second login port, not more users on 1884: 1884 uses the user name as the client id (so the car cannot take another client's id). The fleet checkers share one user and can run at the same time with their own ids, so they need a listener without that rule. Its own password file means the car's password does not work on 1885.
  • 1883 on 127.0.0.1, not removed: the tools that run on routy keep working with no change; only the clients on other hosts must move.
  • One shared fleet-checker user for the checkers on all hosts: per-host users would put host names in this public repo.

Progress

  • Client list (by client id, what each reads and writes) in docs/mqtt-car-user.md
  • Each client has a user and an ACL in the repo (no passwords)
  • The published port needs a login (1883 is no longer anonymous to the outside)
  • CI test: each user can do only its own topics; anonymous on the published ports is refused (.github/scripts/test-mqtt-car-user/run.sh, checks g and h)
  • Review (one round, notes fixed; CI green)
  • PR merged (waits for Geno: the deploy after the merge cuts the outside clients that still use 1883)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant