A selector would allow to only get the messages of the client but it
would not prevent a malicious client to do otherwise. So from a security
standpoint that does not help.
I see two main options here:
1. Use separate reply queues for each client. The easiest way is to just
use the default (temp queues). So the clients do not see each other at all
2. Encrypt the reply message with a key only the client knows. e.g.
public/private key scheme.
Christian
Am 01.01.2012 11:45, schrieb Filippo Balicchia:
Hello,
Why don't use message selector from client point of view ?
--Filippo
Il 31 dicembre 2011 19:57, mgiammarco<mgiamma...@gmail.com> ha scritto:
Hello,
if I have multiple clients that put messages in a queue managed by Camel AND
each client can receive as a reply many messages how can I do it with Camel?
I mean suppose that I create an "out" queue where all replies go. How can I
be sure that a client can get ONLY its messages?
Does Camel put the Principal (user authenticated) in the header of the
message?
Is there a "standard" way that I have not found in the documentation?
Thanks in advance for any reply!
Mario
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-level-authentication-tp5112517p5112517.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
