Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of mgiammarco@gmail.com)
Date: Sun, 1 Jan 2012 03:31:54 -0800 (PST)
From: mgiammarco <mgiammarco@gmail.com>
To: users@camel.apache.org
Message-ID: <1325417514830-5113046.post@n5.nabble.com>
In-Reply-To: 
 <CAP9Z6QnDVmoEVE-mNWpk1hpU-9s2r0Gn_X5=Ohz2CMLGDCiG1A@mail.gmail.com>
References: <1325357856381-5112517.post@n5.nabble.com>
 <CAP9Z6QnDVmoEVE-mNWpk1hpU-9s2r0Gn_X5=Ohz2CMLGDCiG1A@mail.gmail.com>
Subject: Re: Message level authentication
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Thanks for reply in the first day of the year (and BUON ANNO!).

I will consider this thing but I am worried about two things:

- security: can one client "steal messages from others?"
- automation: it seems to me that it is a manual way. Is there an "official
way" to do it? For example to put a token/nonce/principal from value from
spring security (or oauth) in the header of the message?

I have supposed that mine was a common problem.

Thanks again,
Mario

--
View this message in context: http://camel.465427.n5.nabble.com/Message-level-authentication-tp5112517p5113046.html
Sent from the Camel - Users mailing list archive at Nabble.com.