Note that there are some explanatory texts on larger screens.

plurals
  1. POWSO2 ESB applying security policies at binding hierarchy
    primarykey
    data
    text
    <p>I am trying to apply multiple security policies to a proxy service defined in WSO2 ESB 4.0.3. I need to apply one policy at operation level and other at message level. </p> <p>I am using source view to directly define proxy service instead of using Web UI/Policy Editor. </p> <p>I tried defining each policy as described here: </p> <p><a href="http://docs.wso2.org/display/ESB403/Policies+for+Service" rel="nofollow">http://docs.wso2.org/display/ESB403/Policies+for+Service</a></p> <p>but generated WSDL shows it is getting applied at wrong hierarchy. </p> <p>Please advice if this capability is supported in WSO2 ESB or am I doing wrong!</p> <p>My Proxy </p> <pre><code>&lt;proxy name="StockQuoteProxy" transports="https http" startOnLoad="true" trace="disable"&gt; &lt;target endpoint="SimpleStockQuoteService_noSuspendOnFailure_TCPMon"&gt; &lt;inSequence&gt; &lt;header xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" name="wsse:Security" action="remove"/&gt; &lt;/inSequence&gt; &lt;outSequence&gt; &lt;send/&gt; &lt;/outSequence&gt; &lt;/target&gt; &lt;publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_3.wsdl"/&gt; &lt;policy key="sec_operation-Policy"/&gt; &lt;policy key="sec_InOut-Policy"/&gt; &lt;enableSec/&gt; &lt;/proxy&gt; </code></pre> <p>My message level Policy </p> <pre><code>&lt;wsp:PolicyAttachment wsu:Id="Service_message_policy_attachment" 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" xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"&gt; &lt;wsp:AppliesTo&gt; &lt;policy-subject identifier="binding:soap11/operation:getQuote/in"/&gt; &lt;policy-subject identifier="binding:soap12/operation:getQuote/in"/&gt; &lt;/wsp:AppliesTo&gt; &lt;wsp:Policy wsu:Id="Service_message_policy"&gt; &lt;wsp:ExactlyOne&gt; &lt;wsp:All&gt; &lt;sp:SignedParts&gt; &lt;sp:Body /&gt; &lt;sp:Header Name="To" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="From" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="FaultTo" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="ReplyTo" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="MessageID" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="RelatesTo" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;sp:Header Name="Action" Namespace="http://www.w3.org/2005/08/addressing" /&gt; &lt;/sp:SignedParts&gt; &lt;sp:EncryptedParts&gt; &lt;sp:Body /&gt; &lt;/sp:EncryptedParts&gt; &lt;/wsp:All&gt; &lt;/wsp:ExactlyOne&gt; &lt;/wsp:Policy&gt; &lt;/wsp:PolicyAttachment&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload