Message level different policy support is not working at Rampart/C level
-------------------------------------------------------------------------
Key: RAMPARTC-84
URL: https://issues.apache.org/jira/browse/RAMPARTC-84
Project: Rampart/C
Issue Type: Bug
Affects Versions: Current
Reporter: Manjula Peiris
Assignee: Malinda Kaushalye Kapuruge
Priority: Critical
Fix For: 1.2.0
When we attach policies in operation's message direction lable (in
services.xml), Rampart/c does not secure the message as required l. Instead it
takes both the incoming and outgoing policy are same and secure message. This
will fail when incoming path and outgoing path policies are different.
Following is an example.
<operation name="echo">
<messageReceiver
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
<actionMapping>urn:echo</actionMapping>
<message label="in">
<wsp:Policy wsu:Id="SigEncrMessage"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
<sp:SignedParts
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
<sp:Body/>
</sp:SignedParts>
<sp:EncryptedParts
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
<sp:Body/>
</sp:EncryptedParts>
</wsp:Policy>
</message>
<message label="out">
</message>
</operation>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
