Hi Vavricka, The current implementation of ACL in java Broker supports only wildcard character '*' at the end of the property value. Thus, when setting routingKey="test.*, the messages with routing key starting with "test." would be allowed to publish regardless the number of words split by dot.
Regarding wildcards '#', they can be used in binding keys for binding queues to topic exchanges. They have no special meaning in routing keys when publishing messages. Kind Regards, Alex On 12 April 2017 at 13:37, Vavricka <[email protected]> wrote: > I apologize for the part regarding "*" wildcard. I connected to different > broker where ACL rules were different and therefore Java Broker correctly > forbid access. > > Wildcard "*" is working, but behavior is different than in topic exchange > (https://qpid.apache.org/releases/qpid-java-6.1.2/java- > broker/book/Java-Broker-Concepts-Exchanges.html). > It seems to me when I set routingKey="test.*" in ACL, rule matches every > message with routing key starting with "test." and it does not care about > number of words split by dot (like in topic queue). > > Using "*" as wildcard is ok for me. I was just confused that ACL wildcard > works differently from topic exchange. > > Vavricka > > > > -- > View this message in context: http://qpid.2158936.n2.nabble. > com/Java-Broker-Access-control-rights-routingKey-and- > wildcard-tp7662212p7662213.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
