You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Rawad Assaf <ra...@gmail.com> on 2017/01/26 11:21:00 UTC

[Dispatch Router] Permission to create destination

Hello,

I am trying to showcase an example where a dispatch router instance is used
as medium for AMQP based point-to-point messaging between a client and a
server.

In my example, the server creates a JMS consumer on a queue and the client
sends messages to it. I noticed that as soon as the server creates the
consumer the destination is created on the dispatch side and it appears on
the *qdstat* output. This made me think that the dispatch could be easily
flooded with consumer creation requests on random queues. My question is
thus, is there any way to prevent automatic creation of destinations on the
dispatch side and assign this permission to authorized services only?

Thanks!
Rawad

-- 
Rawad.

Re: [Dispatch Router] Permission to create destination

Posted by Rawad Assaf <ra...@gmail.com>.
Clear! Thanks!!

On 26 Jan 2017 22:01, "Chuck Rolke" <cr...@redhat.com> wrote:

> Hi Rawad,
>
> Dispatch Policy http://qpid.apache.org/releases/qpid-dispatch-0.7.0/
> book/book.html#policy
> can do just that. Policy can deny or allow consumer sources and sender
> targets. Dispatch
> will always create the address internally if the policy allows the user to
> access it.
>
> Sample policies are used for self test in directories
> qpid-dispatch/tests/policy*.
>
> -Chuck
>
> ----- Original Message -----
> > From: "Rawad Assaf" <ra...@gmail.com>
> > To: users@qpid.apache.org
> > Sent: Thursday, January 26, 2017 6:21:00 AM
> > Subject: [Dispatch Router] Permission to create destination
> >
> > Hello,
> >
> > I am trying to showcase an example where a dispatch router instance is
> used
> > as medium for AMQP based point-to-point messaging between a client and a
> > server.
> >
> > In my example, the server creates a JMS consumer on a queue and the
> client
> > sends messages to it. I noticed that as soon as the server creates the
> > consumer the destination is created on the dispatch side and it appears
> on
> > the *qdstat* output. This made me think that the dispatch could be easily
> > flooded with consumer creation requests on random queues. My question is
> > thus, is there any way to prevent automatic creation of destinations on
> the
> > dispatch side and assign this permission to authorized services only?
> >
> > Thanks!
> > Rawad
> >
> > --
> > Rawad.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>

Re: [Dispatch Router] Permission to create destination

Posted by Chuck Rolke <cr...@redhat.com>.
Hi Rawad,

Dispatch Policy http://qpid.apache.org/releases/qpid-dispatch-0.7.0/book/book.html#policy
can do just that. Policy can deny or allow consumer sources and sender targets. Dispatch
will always create the address internally if the policy allows the user to access it.

Sample policies are used for self test in directories qpid-dispatch/tests/policy*.

-Chuck

----- Original Message -----
> From: "Rawad Assaf" <ra...@gmail.com>
> To: users@qpid.apache.org
> Sent: Thursday, January 26, 2017 6:21:00 AM
> Subject: [Dispatch Router] Permission to create destination
> 
> Hello,
> 
> I am trying to showcase an example where a dispatch router instance is used
> as medium for AMQP based point-to-point messaging between a client and a
> server.
> 
> In my example, the server creates a JMS consumer on a queue and the client
> sends messages to it. I noticed that as soon as the server creates the
> consumer the destination is created on the dispatch side and it appears on
> the *qdstat* output. This made me think that the dispatch could be easily
> flooded with consumer creation requests on random queues. My question is
> thus, is there any way to prevent automatic creation of destinations on the
> dispatch side and assign this permission to authorized services only?
> 
> Thanks!
> Rawad
> 
> --
> Rawad.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org