camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: How can Shiro be used with camel to limit access to a route?
Date Fri, 06 Apr 2012 07:11:44 GMT
On Thu, Apr 5, 2012 at 8:54 PM, mgiammarco <mgiammarco@gmail.com> wrote:
> Ok I have found the bug:
>
> ShiroSecurityTokenInjector creates a bytearray and puts it in the message
> header.
>
> The bytearray do not pass through openwire...
>

Ah crap, yeah JMS spec have limitations on what can be transfered over
JMS in JMS properties.
We have some notes about this at the Camel JMS wiki page
http://camel.apache.org/jms

I wonder if we can always safely convert the shiro token as a String
representation instead of byte[]?
A string is always supported.

I dont assume we need to base encode the byte array or something? The
token may already be representable out of the box in a String.

Maybe you could check a bit on Shiro and see about this about the
token? And if possible we could maybe adjust the code in camel-shiro.

> But the bytearray content is a string text with only ascii chars! So I
> manually put it as an header of string type.
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/How-can-Shiro-be-used-with-camel-to-limit-access-to-a-route-tp5521623p5621207.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message