ODE supports securing of partner links. What you have to do is specify the policy as described in the user guides "How to use WS-Security in ODE" section[1]. Refer "How to invoke a secured web service" sub section. What you have to do is specify the policy file to use with the service invocation in a endpoint configuration file as following. Policy file location is absolute.
alias.sample03-ns=http://sample03.policy.samples.rampart.apache.org sample03-ns.sample03-policy.ode.security.policy.file=mypolicy.xml Look at the sample located at ODE_TRUNK/axis2-war/src/test/resources/TestRampartPolicy. Thanks Milinda 1. http://ode.apache.org/user-guide.html#UserGuide-QuickRampartintroduction On Mon, Sep 28, 2009 at 2:27 PM, Filip Majernik <[email protected]>wrote: > Hi, > I have following problem. When using ODE with AXIS2 as IL there's a > possibility of using the Rampart security modul. Then I can define > WS-SecurityPolicy and attach it to the web service defined by that process. > Now, as of axis2 1.4 (which comes with ODE 2.0 beta) a WS-SecurityPolicy > can > be attached to the service at binding level, operation level and message > level. Let's say I have a simple process with receive, invoke and reply > activity. The web service I am invoking is defined through a PartnerLink > and > that's why the policies I attached at any of that levels won't apply. Can I > somehow attach the WS-SecurityPolicy to the messages exchanged in that > PartnerLink (or define what has to be encrypted) ? > > Thank you in advance, > Filip > -- Milinda Pathirage Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps WSO2 Inc.; http://wso2.com E-mail: [email protected], [email protected] Web: http://mpathirage.com Blog: http://blog.mpathirage.com
