[
https://issues.apache.org/jira/browse/AMQ-9472?focusedWorklogId=913540&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-913540
]
ASF GitHub Bot logged work on AMQ-9472:
---------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/24 23:46
Start Date: 08/Apr/24 23:46
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #1198:
URL: https://github.com/apache/activemq/pull/1198#issuecomment-2043874595
I think that the behavior should match the destination policy.
1. Wildcard
2. Fully qualified name (authoritative)
I agree, it should be a new flag since we would not want to change behavior
on existing users.
Issue Time Tracking
-------------------
Worklog Id: (was: 913540)
Time Spent: 1h (was: 50m)
> Wildcard publisher auto-creates wildcard topic and breaks authorization
> -----------------------------------------------------------------------
>
> Key: AMQ-9472
> URL: https://issues.apache.org/jira/browse/AMQ-9472
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker
> Reporter: Albertas Vyšniauskas
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
