Hi, Yikes, that is indeed an issue if the token is not propagated via ActiveMQ. I believe Camel headers should be propagated to custom JMS headers and picked up on the other end by a Camel Route and preserved.
If this is not happening, this is definitely a bug. The bug could be somewhere between the Shiro and JMS component... Can you please go ahead and log a Apache JIRA ticket for the same at the following link https://issues.apache.org/jira/secure/Dashboard.jspa https://issues.apache.org/jira/secure/Dashboard.jspa I will also try this out at my end in the next day or two and see what is going on... Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/How-can-Shiro-be-used-with-camel-to-limit-access-to-a-route-tp5521623p5526376.html Sent from the Camel - Users mailing list archive at Nabble.com.
