Hi, Mark:<div><br></div><div>See the convenient table in�<a href="http://www.rabbitmq.com/access-control.html">http://www.rabbitmq.com/access-control.html</a></div><div><br></div><div>To prevent publishing, deprive your client of the write privilege for the exchange in question. �Creating queues will require the configure permission on the queue's name, and binding the newly created queue to the exchange requires you to be able to write the queue and read the exchange.</div>
<div><br></div><div>More exotic limitations are possible if you write your own custom auth backend, although that will require you to write Erlang code and understand a few of Rabbit's internal interfaces, how to compile a plug-in, etc.</div>
<div><br></div><div>Best regards,</div><div>Jerry</div><div><br><div class="gmail_quote">On Tue, Sep 18, 2012 at 8:58 AM, Mark Everett <span dir="ltr"><<a href="mailto:quortex@gmail.com" target="_blank">quortex@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey,<br><br>I need to be able to make a client create queues when they do not exist and read from queues. However, I do NOT want the client to be able to write messages to the queue.<br>
<br>Is this possible? Thanks in advance.<br><br>Cheers,<br>Mark<br><br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>