[AMQ-9472] Wildcard publisher auto-creates wildcard topic and breaks authorization

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Component/s: Broker
• Assignee: Jean-Baptiste Onofré
• Reporter: Albertas Vyšniauskas
• Created: 06/Apr/24 08:02
• Updated: 10/Apr/24 15:49
• Resolved: 10/Apr/24 15:49

Description

Hi,

after publishing a message to wildcard topic, a wildcard topic is auto-created and interacts poorly with authorization rules.

Suppose that authorization map contains the following entries:
<authorizationEntry read="admin" write="admin" admin="admin" topic=">" />
<authorizationEntry read="user" topic="A.B" />

Admin creates "A.B" topic and publishes a message to "A.>" causing auto-creation of "A.>" topic.

User attempts to consume "A.B" topic, but receives "User user is not authorized to read from: topic://A.>" error.

I asked on user mailing list if wildcard publishing is supposed to work at all, as I could not find any documentation about that. Unfortunately I did not receive any response, so I have to assume that it does.

Issue Links

• relates to: AMQ-9475 ConsumerControl commands for wildcard consumers should not auto-create destinations