A broker still open on default credentials

Still guest and guest. I never got around to changing it.

Beginner to intermediateRead 4 minDoing: under an hour5 steps

▶ Start

What you'll have at the end

A broker with the default guest account disabled and a scoped-permission user in its place

Before you start

You need

A running message broker your services already connect to, still using its out-of-the-box guest account, and at least one real service that talks to it you can point at new credentials.

Not covered

Switching to an outside authentication backend like LDAP or OAuth 2 instead of the broker's own built-in user list.

Leans on

RabbitMQ Message Broker Cheat Sheetthe three-scope permission model (configure, write, read) and the tags table this recipe compares guest against both live in its Security and Access Control table.
Message Queues Cheat Sheetthe general access-control vocabulary this broker-specific fix sits underneath, in its Security table.

5 steps

Checked 19 Aug 2026

Part of the Message Queues cookbook