Mosquitto That Asks Who You Are

Mosquitto (MQTT) with accounts: the package starts in local-only mode with anonymous clients allowed, no persistence directory and no packet-size limit. This role writes a listener that refuses anonymous and wrong-password clients (proved live), keeps retained messages across restarts, caps packets at 1 MiB, and renders topic ACLs from a list. Original role, live-tested on Rocky Linux 10.

ansibleMessaging & Streaming

Verification

Live-tested

Really deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.

Conformance

  • Static validation (yamllint · ansible-lint)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-09-19 · podman 4.9.3 · ansible 2.21.4 · how we verify

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: live-tested](https://www.iac-bazaar.com/api/artifacts/ansible-mosquitto-broker/badge)](https://www.iac-bazaar.com/catalog/ansible-mosquitto-broker?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Ansible role 1.0.0, live-tested on IaC Bazaar: [Mosquitto That Asks Who You Are](https://www.iac-bazaar.com/catalog/ansible-mosquitto-broker?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```yaml
# Mosquitto That Asks Who You Are: https://www.iac-bazaar.com/catalog/ansible-mosquitto-broker (download from your IaC Bazaar account)
```

Preview:IaC Bazaar: live-tested

Documentation

mosquitto-broker

Mosquitto (MQTT) with accounts, persistence and a packet-size limit. Original role for EL 10, live-tested with podman on Rocky Linux 10.

Mosquitto is in EPEL. AppStream on EL 10 has no MQTT broker; the role enables EPEL first (mosquitto_broker_enable_epel: false if you mirror it).

The package lets anyone in. Its mosquitto.conf is comments only, so Mosquitto 2 starts in "local only mode": port 1883 on loopback, anonymous clients allowed. The live test published and subscribed with no credentials against the package as shipped. Local-only is not a boundary on a host that runs anything else - every process on it may read and publish every topic. This role writes an explicit listener with allow_anonymous false and a password file, and the live test proves anonymous and wrong-password clients are refused before it round-trips a message through an account.

Passwords are written by mosquitto_passwd, not rendered. It salts every hash, so a templated file would change on every run. The role adds an account only when it is missing from the file (or all of them when mosquitto_broker_reset_passwords is true), which is what keeps the second run at changed=0. Removing an account is yours to do.

Nothing survives a restart, and nothing is too big. Persistence is off and its directory does not exist, so retained messages and durable subscriptions are lost on restart; max_packet_size is 0, so a client may send 256 MiB in one message. The role turns persistence on in /var/lib/mosquitto/ and caps packets at 1 MiB; the live test publishes 2 MiB and expects a refusal.

Topic ACLs are one list away. mosquitto_broker_acls renders an acl_file; empty means every account may use every topic.

License

Commercial - IaC Bazaar EULA. (c) IaC Bazaar.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Variables
  • Test

Related modules

Live-tested

ansible-kafka

Apache Kafka 4 (SHA-512 pinned) on Java 21, one KRaft node on EL 10 from the upstream release, as a hardened systemd service on loopback; the live test creates a topic, produces one message, consumes it back and reads the metadata quorum; the metadata log is formatted once as the service user and the root-owned release tree is run in place. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-dovecot

Dovecot from AppStream: IMAP for your mail clients and LMTP for your MTA, Maildir in each home, TLS required before any login, a minimum TLS version checked before it lands, and every listener on loopback until you open it. The live test delivers over LMTP, reads the message over IMAPS, and sees a plaintext login from another address refused. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-gotify

Gotify on EL 10 from the vendor's release, pinned by a SHA-256 the role carries (the vendor publishes no checksum file), as a hardened systemd service on loopback with its settings in an EnvironmentFile; the live test creates an application, pushes a message with its token, reads it back as the admin, and sees a wrong password and a bad token refused. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-postfix-tls

An EL host opens no submission service, so every client sends on port 25 where plaintext is accepted. This role adds 587, which refuses mail until the session is encrypted, and 465, which is TLS from the first byte. Port 25 keeps taking plaintext on purpose and the live test asserts it, because a mail exchanger that demands STARTTLS loses mail. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-nats

nats on EL 10 from the GitHub release; get_url refuses it unless its SHA-256 is in the vendor's checksums file, and the live test re-checks it, then saves a context under a throwaway config home, reads it back, and runs server check connection against a dead port expecting exit 2 and CRITICAL. Pinned. Original role, live-tested on Rocky Linux 10.

View module
Live-tested

ansible-nats-server

NATS server from the upstream release (sha256-verified) as a hardened system service on loopback with JetStream under its own data directory and the configuration checked by nats-server -t before it lands. No client is installed, so the live test speaks the protocol itself: one session subscribes, publishes and reads its own message back. Original role, live-tested on Rocky Linux 10.

View module