Bug 707678

Summary: Can't restrict publication to a specific queue
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Chuck Rolke <crolke>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 2.0CC: jross
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 21:28:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Gordon Sim 2011-05-25 17:17:07 UTC 
There is no way it seems to specify the default (nameless) exchange in a publish rule (the routing-key can be restricted of course) as the syntax offers no way to express an empty string as a value.

This means you can't restrict a user to publishing only to a given queue. The rule that does that (e.g. acl allow my-user@QPID publish exchange routingkey=my-queue) will actually allow that user in theory to publish to any exchange as long as the routing-key is my-queue).
Comment 1 Justin Ross 2013-02-26 21:28:33 UTC 

*** This bug has been marked as a duplicate of bug 808105 ***