Hi,
You do not need 5 ShiroConfiguration.ini files. You use a single file to
keep the 5 different authorization policies tied to a given authentication
principal. The policy is simply an enforcement point for information using
rules in the config file.
By applying different policy sets on different route segments, I mean the
following
from("seda:a")
.choice()
.when(header("foo").isEqualTo("bar"))
.policy(MyTimeSensitivePolicy)
.to("seda:b")
.when(header("foo").isEqualTo("cheese"))
.policy(MyCostSensitivePolicy)
.to("seda:c")
.otherwise()
.policy(MyDistancePolicy)
.to("seda:d");
Each of the Policy sets simply reflects a potentially different set of rules
and may share a single config file.
Cheers,
Ashwin...
PS: Shiro rocks!!!...
-----
---------------------------------------------------------
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-tp5521623p5526359.html
Sent from the Camel - Users mailing list archive at Nabble.com.
